Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 451901 - Automatically add "NOT RESOLVED" resolution state to all groups upon creation
Summary: Automatically add "NOT RESOLVED" resolution state to all groups upon creation
Keywords:
Status: NEW
Alias: None
Product: Issue-Tracker
Classification: Retired
Component: User Interface
Version: 4.6
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Lisa Lu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-18 01:27 UTC by Gary Case
Modified: 2008-06-18 01:27 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Gary Case 2008-06-18 01:27:16 UTC
Description of problem:
Currently, all tickets automatically receive the "NOT RESOLVED" state upon
creation. If you visit the Groups > (group name) > Resolutions link for a group,
"NOT RESOLVED" is not automatically on the list. This means that, if you add a
new resolution state and don't add "NOT RESOLVED" too, all your tickets will
pick the newly added resolution code upon next update. The Resolutions list
needs to have "NOT RESOLVED" automatically populated on group creation.

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

How reproducible:
Always

Steps to Reproduce:
1. Log in to IT as a Red Hat employee
2. Go to Groups > (group name) > Resolutions for a newly created group
3. NOT RESOLVED isn't present in the right-hand column.
  
Actual results:
"NOT RESOLVED" isn't automatically on the list of resolution codes for groups,
even though all tickets have that resolution code upon ticket creation.

Expected results:
"NOT RESOLVED" is automatically on the list of resolution codes for groups upon
group creation.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.