I understand that editing global workflows requires JIRA admin status, but we recently pared down our jira-admin users group severely, as it was getting out of control. So, we made specific people administrators of their individual projects, but they can't switch workflow schemes on their projects. So, they'll click on the project settings button, select workflows, but don't see the button to switch workflows.
Is that by design, or am I missing something?
JIRA has 3 different "levels" of access.
Workflows, Screens, Permissions, etc. can only be updated at the second level; you can grant more people not only members of administrators group, but you can´t restrict the access by project (all who can update a workflow, could update every workflow, not just their owns)
Very similar situation here where we cleaned up and reduced our global admins. However, as part of this reduction in rights, project admins wanted to be sure they could select the schemes for issue types, field configurations, workflows, etc. Not CHANGE them, just select the one they want to apply to their project. As I'm reading this answer, am I to understand that switching schemes is not something project administrators can do?
Atlassian are moving in a slightly different direction to allow project admins more control, but project admins only have control over users, versions and components, and, if you are on 7.3 and your workflow is not shared, some edit rights over that.
You can take a look at Wittified's Delegated Project Admin Pro for JIRA which does exactly this:
Disclaimer: I work for Wittified...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot