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 452168 - Clearly indicate or remove dependency on "Group Tech" privilege for "Escalate" privilege.
Summary: Clearly indicate or remove dependency on "Group Tech" privilege for "Escalate...
Status: NEW
Alias: None
Product: Issue-Tracker
Classification: Retired
Component: User Interface
Version: 4.6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Lisa Lu
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-19 19:20 UTC by Gary Case
Modified: 2008-06-19 19:20 UTC (History)
0 users

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

Attachments (Terms of Use)

Description Gary Case 2008-06-19 19:20:20 UTC
Description of problem:
The individual user group privilege currently called "Group Tech" is required in
addition to the "Escalate" privilege to escalate a ticket to an escalation
group. This dependency should either be immediately indicated (pop up saying
"Group Tech privilege is required along with Escalate in order to escalate
tickets" if a user attempts to grant "Escalate" without "Group Tech" already
being chosen) or the dependency should be removed and the "Escalate" privilege
should allow escalation on its own (unlock the "Ownership" section when chosen).

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

How reproducible:

Steps to Reproduce:
1. Log in to IT as RH employee
2. Go to Groups > (group name) > Privileges
3. View the "Escalate" privilege
Actual results:
Granting "Escalate" doesn't work unless Group Tech also granted.

Expected results:
"Escalate" should work on its own or warn you about additional steps needed to

Additional info:
A name change from "Group Tech" to "Edit Header" has been proposed in BZ 452167.

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