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

Key: JRA-12127
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Duplicate
Priority: Major Major
Assignee: Unassigned
Reporter: Carter Snowden
Votes: 0
Watchers: 0
Operations

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

delegate admin tasks to the project level

Created: 09/Feb/07 07:00 AM   Updated: 04/Mar/07 06:38 PM
Component/s: Project Management
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Participants: Carter Snowden and Nick Menere [Atlassian]
Since last comment: 75 weeks, 1 day ago
Resolution Date: 12/Feb/07 09:17 PM
Labels:


 Description  « Hide
We're running multiple, diverse projects with separate permission schemes such that those with jira accounts can see only those projects for which they have permissions (and any projects with world-readable elements). No one in any of the groups associated with a particular project has global jira-administrators privileges, though the small, central, jira-administrators group does have admin and browse permission in all permission schemes.
The project leads of the various projects have varying needs as regards workflows, notification schemes, etc. As it is now, the central jira-administrators group needs to create workflows/notification schemes and assign them to the various projects. As far as I can tell, there is no way to delegate workflow/notification creation and editing to any person or group other than jira-administrators. Since jira-administrators creates the scheme and then assigns it to a project, it seems, on the face of it, reasonable to be able to allow project leads/project admin groups to create their own workflows/workflow/notification schemes from the get-go and edit them from there on.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Nick Menere [Atlassian] - 12/Feb/07 09:17 PM
Carter,

The issue is already being tracked at JRA-3156.
Please read through the description and comments and add anything you feel may be beneficial.

Cheers,
Nick