Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hello together,
as the title suggests, i´m looking for a way to allow project admins to edit workflows.
I read somewhere that it´s a new feature since a few days and I would like to know where to find this setting. I hope its also available in 7.3...
Thanks ;-)
Yes, it's a new feature in 7.3 but comes with some conditions.
Please read below (from the release notes of 7.3)
Project level administration
We've extended the project administrators permission, so that project administrators can now edit their projects workflow under certain conditions:
The project admins will not be able to edit the workflow to the same extent as a JIRA administrator. The restrictions are:
This feature is enabled by default. When you upgrade to JIRA Software 7.3, all your project administrators will have access to this feature immediately. To edit a workflow, a project administrator should select Project settings in their project's sidebar, and select an issue type. This will present the workflow, and Edit Workflow will be available.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the quick help. I followed all the steps but it still doesn´t work.
I gave the project admin the permission through the permission-scheme but he still can not edit the workflows in any way.
Is there some other possibility to make this work?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is the workflow only used by that one project? Make sure the workflow scheme is not shared and the workflow is not in more than one scheme.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic,
yes, there are 2 workflows and both are not shared with any other projects. Also, none of them are jira default workflows.. so that really confuses me why it isnt working.
Edit: I just saw that the permission scheme is shared by 5 projects and that its a default permission scheme. But that has nothing to do with the workflows. Or is it also relevant that the permission scheme has to be separate from the other projects?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, the permission scheme does not matter.
What does the project admin see when they go to the project set up and click through to the workflow section?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, What does the project admin see when they go to the project set up and click through to the workflow section?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry Nic, I dont understand what you mean then :-(
The project admin can see all the workflows that are available in that project. He can see the different types of processes i.e. Project, specification, feedback, bug, task etc.. but cant edit them at all, the option to do so isnt there in the first place..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I need you to check Project settings -> Issue type and see if the edit link is there.
If it is not, then the workflow is shared with another project
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I mentioned earlier, the edit button / link is not there. So no, it does not appear.
No, there are only 2 workflows in the project and none is shared with another project.
In other projects where the workflows are shared there is a note saying "Workflow shared with 6 projects etc.).
But not the two from the mentioned project, they are unique to it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am unable to replicate what you're seeing. I either have to remove project admin rights from my account or share the workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic,
did you have any luck with the problem?
I think that if this doesn´t work, i´ll give the worker full rights to the project although thats not the best way..
Thanks ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, as I said, I really cannot replicate it. I either have to remove project admin rights from my account or share the workflow to disable my edit option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Apparently, this does not work in JIRA Cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's working fine in Cloud, in the project types that support Simplified Workflows (Software Company Managed projects are the only types that implement them)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the restrictions in place are extremely limiting. Most of the work I've had to do over the years comes from the things you're not allowing a project admin do, so the new "features" of allowing admin role to change stuff, is pretty useless in my use case. I hoped to grant more power to project owners, as it should be.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A project admin should be able to update issue types schemes and workflow schemes (adding issue types and splitting issue types to their own workflows) and screen schemes and field configuration schemes (making fields required and assigning screens to issue types), as well as changing workflow transition screens and adding/editing post functions and other transition properties. These are all vital to our project management process and this is where most of my time is spent, rather than being a sr. systems engineer. What's up with not being able to change a project category? That one seems pretty innocuous.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I opened a few tickets for granting additional options to project administrators:
Advanced Workflow: https://jira.atlassian.com/browse/JRASERVER-68689
Fields: https://jira.atlassian.com/browse/JRASERVER-68690
Issue Types: https://jira.atlassian.com/browse/JRASERVER-68692
Screens and Field Configs: https://jira.atlassian.com/browse/JRASERVER-68693
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Tarun Sapra @Nic Brough -Adaptavist-
My question exactly is . In the documentation it's mentioned that :
But in my instance the project administrator can delete status in workflow .
Im reviewing the certefication so i need to know exactly if he can or can't
Best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looks like the feature is only available in Jira 7.4 onwards: https://jira.atlassian.com/browse/JRASERVER-3156
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.