Permissions: what level to edit workflows?

I am currently a project administrator (not the over-all admin). Is the ability to edit workflows restricted to only the over-all administrators?

2 answers

1 accepted

Accepted Answer
6 votes
Marian Finch Atlassian Team May 20, 2013

Hey Tyler,

In order to edit workflows you would need to have the JIRA Administrators global permission. The Administer Projects permission allows you to edit project role membership, project components, project versions and some project details ('Project Name', 'URL', 'Project Lead', 'Project Description') - (see our doc on Managing Project Permissions for more information). Feel free to email sales@atlassian.com and ask for Marian if you have any additional questions :)

Hi @Marian Finch is this answer still valid for the latest version of JIRA? 

No, it's not, the post is almost 5 years old.

To edit a workflow, you must be:

  • An administrator.
  • If you have Jira Software, then an admin can "simplify" the workflow, and board admins can then edit it to some extent.
  • If you are a project admin, and have Jira 7.3 or above, and your workflow is only used by your project, then you can also make some limited edits to it
  • If you have Jira 7.4+, the right to edit the workflow (if it is limited to one project) now becomes a permission setting for the full admins to set if they want.

And, if you are using cloud JIRA, you're currently (Oct 13, 2017) out-of-luck.  Nothing I have seen enables Project Admin-role people to edit their workflows, which is a disappointment.

@Nic Brough [Adaptavist], correct me if i got it wrong, at latest JIRA version we can give for example to a Project Lead the permission to edit workflow for that project?

Yes, as mentioned above.

@Nic Brough [Adaptavist] - How about cloud JIRA these days? would I still be out-of-luck as it was the case with @Steve Craig a few months ago ? I hope not (fingers crossed), please let me know

Jack Brickey Community Champion Mar 23, 2018

@Yazan Hijji, please read here for available permissions

Server only so far

Ok got it :( , thanks!

3 votes

Marian is right for plain Jira, but you've used "greenhopper" as well. IF your system adminstrators set the "simplified workflow" flag on your project, then you'll be able to define your own workflow by setting columns as a project administrator.

but we are losing the ability to have screens that captures values during the transitions. besides there are known issues as per the documentation

Correct. Simplified workflow IS simplified - no transistion screens etc. That's the point, it's supposed to be more simple.

I'm not sure what you mean by "known issues"?

I was referring to https://confluence.atlassian.com/display/GHKB/Unable+to+set+issues+to+Resolved+using+Greenhopper+Simplified+Workflow.

I just wish the JIRA workflow would be more preferable to be able to accessed by a project lead. As a matter of fact, Project Admins should be able to perform all of the admin tasks for that particular project without been given with a global admin access as that would be exposing everything and risky as I have recently seen that one of the admin has deleted an important project altogether may be by mistake.. but that cost my precious time to figure out what happened and eventually restore from backup, the sad part is I cannot trace who did that since the audit log is not there by design for administrative events. I tried searching the logs with no luck.

I was referring to https://confluence.atlassian.com/display/GHKB/Unable+to+set+issues+to+Resolved+using+Greenhopper+Simplified+Workflow.

I just wish the JIRA workflow would be more preferable to be able to accessible by a project lead. As a matter of fact, Project Admins should be able to perform all of the admin tasks for that particular project without been given with a global admin access as that would be exposing everything and risky as I have recently seen that one of the admin has deleted an important project altogether may be by mistake.. but that cost my precious time to figure out what happened and eventually restore from backup, the sad part is I cannot trace who did that since the audit log is not there by design for administrative events. I tried searching the logs with no luck.

That issue is fixed in later versions.

There's a request outstanding for more granular permissions, and Atlassian are looking at it. Sadly, it's not as simple as it looks, both in terms of code and logic - your definition of "admin tasks for a project" could well be very different for another user. But it is in progress, rather than parked with "not in the next year"

I would love to see a status update on this item from 2013.  In 2017, with Cloud Jira, do we still need to give away super-admin privs to people if we only want them to be able to modify workflows? @Nic Brough [Adaptavist] and @Marian Finch  Greenhopper is not an option for us, thanks!

It hasn't been Greenhopper for years.  It's JIRA Software now.

JIRA 7.3 gives you another option alongside JIRA Software's "simplified workflow".  Project admins can make limited edits to a workflow IF that workflow is not shared with other projects. 

7.4 added a specific permission for allowing it because most of the user-base demanded the ability to turn it off before the project admins made a mess with it!

Hurray!  Thanks for the quick reply @Nic Brough [Adaptavist]!  How do i tell if my Cloud Jira is version one-of-those-you-mentioned, because this doesnt sound anything like 7.3 or 7.4:

License Information for JIRA

JIRA v1001.0.0-SNAPSHOT

Cloud has diverged from Server and uses a different numbering scheme.  It is "on the latest version" though, generally ahead of Server.  I don't know if it has that function actually.  Have a look at a permission scheme to see if there is an "advanced admin" option.

I've been looking around now for a little while, and it certainly appears to me that my version of CloudJira does not contain the ability to delegate workflow editing to Project Administrators.

 

I'd love to hear an offical response from Atlassian as to where this is on the cloud jira roadmap so that I can appropriately set my client's expectations.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Apr 22, 2018 in Jira Software

How-to setup a secured Jira Software 7.9.0 on Ubuntu 16.04.4 in less than 30 minutes

...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...

1,744 views 14 13
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you