Bug 451879 - Retitle "Move Issues" group permission to "Change Escalation Group" for Red Hat employees
Summary: Retitle "Move Issues" group permission to "Change Escalation Group" for Red H...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Issue-Tracker
Classification: Retired
Component: User Interface
Version: 4.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Lisa Lu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-17 22:39 UTC by Gary Case
Modified: 2020-03-27 17:35 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 17:35:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Gary Case 2008-06-17 22:39:56 UTC
Description of problem:
The "Move Issues" group permission is confusingly named. For Red Hat Employees
without the Admin privilege (most employees), this privilege grants the ability
to move a ticket between escalation groups, not base groups. The current
descriptor of "Move Issues" insinuates that you have the ability to move issues
between base groups.

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

How reproducible:
Always

Steps to Reproduce:
1. Log in to IT
2. Visit Groups > (group name) > Privileges
3.
  
Actual results:
Privilege is titled "Move Issues"

Expected results:
Privilege titled "Change Escalation Group"

Additional info:

Comment 1 Gary Case 2008-06-17 22:52:21 UTC
I was originally concerned that this retitle would confuse users with the Admin
privilege (very few users have this, afaik) as they gain the ability to change
the base group as well as the escalation group, but admins should not need this
or any other group permissions to do anything in IT (they're admins, they should
be able to do everything).

Mike or Lisa, I'll open another ticket to request that admins have this
privilege name changed to "Change Escalation or Base Group" if you find that
admin users really need this group privilege to move things between base groups.


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