Bug 452168 - Clearly indicate or remove dependency on "Group Tech" privilege for "Escalate" privilege.
Clearly indicate or remove dependency on "Group Tech" privilege for "Escalate...
Status: NEW
Product: Issue-Tracker
Classification: Retired
Component: User Interface (Show other bugs)
4.6
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lisa Lu
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-19 15:20 EDT by Gary Case
Modified: 2008-06-19 15:20 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gary Case 2008-06-19 15:20:20 EDT
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):
4.6

How reproducible:
Always

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
function.

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.