Bug #7142

activation-key: red border doesn't appears on updating content-host limit with invalid value

Added by Walden Raines over 3 years ago. Updated 3 months ago.

Status:New
Priority:Normal
Assigned To:-
Category:-
Target version:Foreman - Team UX - Backlog
Difficulty:easy Pull request:
Bugzilla link:1131204
Story points-
Velocity based estimate-
ReleaseBacklogRelease relationshipAuto

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1131204
Description of problem:
Found a failure in automation where we are updating the content-host-limit of an existing activation-key with some invalid value (say with some string), and UI doesn't highlight the input box with red border and save button remains disabled.

Please note that this happens only while editing the activation-key. When we use invalid limit while creating activation-key, the red border appears. So the behaviour should be consistent with create activation-key.

Version-Release number of selected component (if applicable):
sat6 GA snap5

How reproducible:
always

Steps to Reproduce:
1. create a activation-key with default content-host-limit
2. update the limit with either string or -ve value
3.

Actual results:
UI doesn't highlight the input box with red border, when we update content-host-limit with some invalid value.

Expected results:
UI should highlight the input box with red border while updating the limit with some invalid value

Additional info:


Related issues

Related to Bastion - Feature #5322: [8] Nutupane: display errors on a per field basis New 04/21/2014

History

#1 Updated by Walden Raines over 3 years ago

  • Related to Feature #5322: [8] Nutupane: display errors on a per field basis added

#2 Updated by Eric Helms over 3 years ago

  • Difficulty set to easy
  • Triaged changed from No to Yes

#3 Updated by Walden Raines over 3 years ago

  • Status changed from New to Assigned

#4 Updated by Walden Raines over 3 years ago

  • Status changed from Assigned to New

I looked into this some and I believe that rewriting our error messages using ngMessages (https://docs.angularjs.org/api/ngMessages/directive/ngMessages) is the way to go. ngMessages is available in Angular 1.3, which is currently in beta, so I am moving this back to "new" status until Angular 1.3 is released.

#5 Updated by Bryan Kearney over 2 years ago

  • Category changed from Web UI to Activation Key

#6 Updated by Eric Helms almost 2 years ago

  • Project changed from Katello to Bastion
  • Category deleted (Activation Key)

#7 Updated by Eric Helms almost 2 years ago

  • Release set to Backlog

#8 Updated by Walden Raines 12 months ago

  • Target version set to Team Tom - backlog

#9 Updated by Walden Raines 3 months ago

  • Target version changed from Team Tom - backlog to Team UX - Backlog

#10 Updated by Walden Raines 3 months ago

  • Assigned To deleted (Walden Raines)

Also available in: Atom PDF