Restricting workflow edit access

[Dheeraj Segapalli]

Any user in the Jira global adminsitrator group can create/modify a workflow. There can be several users related to multiple projects in that group, but how do we restrict that admins to their particular project,board only, so they other workflows in the system can't be edited by them.

For example, user A who is in the global admin group having access to ONLY project A, edit ONLY workflow scheme of A, but not other workflow schemes. 

[Nic Brough -Adaptavist- · Accepted solution]

No, an administrator's job is to look after the whole Jira, they have access to administrate everything.

You should not have lots of global admins, but you should consider delegation - if you have Jira Software, simplifying workflows enables project admins to amend their workflow.  You can also delegate some workflow admin to project admins in later versions of Jira by giving them "extended project admin" in the permission scheme.

[Joe Pitt]

Also, a couple of days off without pay for violating the rules will usually make everyone follow the rules. 

[Dheeraj Segapalli]

Agree that there should be limited number of global admins. Can you elaborate on extended project admin feature?  It would be useful if the project admins can edit the workflow too,

[Nic Brough -Adaptavist-]

Start at https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html

Extended Admin started a while ago, but I can't remember which version added the workflow stuff to it - 7.6 possibly, but it may be later than that.

[Dheeraj Segapalli]

Ok. However, our version is Jira cloud..

[Nic Brough -Adaptavist-]

Ah, yes, this was a feature that is server only.  You don't get it on Cloud.