Bug 517549

Summary: Duplicate Internal Statuses should not be allowed in Issue Tracker
Product: [Retired] Issue-Tracker Reporter: Nicole Yancey <nyancey>
Component: NotificationsAssignee: Lisa Lu <llu>
Status: CLOSED CURRENTRELEASE QA Contact: Nicole Yancey <nyancey>
Severity: urgent Docs Contact:
Priority: urgent    
Version: MR13   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-21 15:19:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nicole Yancey 2009-08-14 15:21:10 UTC
Description of problem: Users can add more than one Internal Status in Issue Tracker.  This should not be allowed.  


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


How reproducible: always


Steps to Reproduce:
1. Login to https://enterprise.stage.redhat.com/issue-tracker as Administrator
2. Go to Internal Statuses
3. Verify Waiting on Collaboration already exist
4. Click on New Internal Status - create another status=Waiting on Collaboration

  
Actual results: duplicate entry allowed


Expected results: Warning message - entry already exist


Additional info: Lisa is aware of issue and will be fixed as part of MR13 IT release

Comment 1 Lisa Lu 2009-08-14 16:21:23 UTC
fix avail for testing on
  http://cspserver2.app.dev.redhat.com

Comment 2 Nicole Yancey 2009-08-14 16:43:24 UTC
The message should be consistent

a) Create new internal status - The internal status entry already exists
b) Update existing entry - duplicated entry

Expected Result - The internal status entry already exists

Comment 3 Lisa Lu 2009-08-14 17:32:36 UTC
Nicole,

I modified the error message on new internal status creation to "duplicated entry
". It can be verified on

  http://cspserver2.app.dev.redhat.com 

Thanks,
Lisa

Comment 4 Nicole Yancey 2009-08-14 18:20:23 UTC
verified in dev and stage

Comment 5 Nicole Yancey 2009-08-14 18:21:03 UTC
(In reply to comment #4)
> verified in dev and stage  

Verified message says - The internal status entry already exists

Comment 6 Nicole Yancey 2009-08-21 15:19:26 UTC
pushed to production 8/18