History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-4176
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Martin Rothbaum
Votes: 7
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
JIRA

Project "sub-commanders"

Created: 05/Aug/04 01:09 AM   Updated: 05/Aug/04 01:10 AM
Component/s: Permissions Security
Affects Version/s: 2.6.1 Enterprise
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Martin Rothbaum
Since last comment: 207 weeks, 1 day ago
Labels:


 Description  « Hide
The main reason why I end up creating additional permission schemes is to allow specific users elevated rights for a particular project. This is quite a common need, as project leaders often need to delegate certain tasks. An example is delegation of "defect management" for a project. Ordinarily, on the assignee, reporter and project lead can edit or re-assign an issue. However the defect manager needs to be able to do this for any issue in the project.

Basically what is needed is a built-in per-project group called "Project Admins" or similar. It would be different for each project (like the project lead is), but could be assigned permissions globally within a scheme.

Alternatively, you could allow permissions to be assigned to the group of Component Leads (implicitely per-project).



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Martin Rothbaum - 05/Aug/04 01:10 AM
This (JRA-4176) is a different slant on JRA-3156, but would be considerably more useful to us.