How to change shared workflows, if I am administrator of project

[Alik]

Hi all. I have a question about project administrator privileges. I am administrator of 2 projects and my workflow scheme, workflow shared only between that two project. Nobody else not using my workflows. When I want to change my workflows Jira show me this notification "This workflow is read-only as it's used by other projects.". I can make modifications if they are not shared with another projects, but I want to make changes and use in two project simultaneously. Extended project administration rights also has been enabled. Any suggestions to do that ? Thanks in advance

My Jira server version 7.12

[saravana kumar]

You can clone that workflow and make changes, then that workflow assigned to the respective project. 

[Alik]

Hi @saravana kumar ,

Thanks for information. I agree with that, but this method need more than one step.

Thanks

[Ganesh Babu]

Hi @Alik 

You can edit the shared workflow only if you are the Jira Admin. Extended Project  Admin permissions will only provide permission to edit if its not shared with other projects. 

So if you want to edit the workflow that is shared you need to be a Jira Admin.

[Alik]

Hi @Ganesh Babu ,

Thanks for informing me. I think this is necessary function to edit workflows, which are only in your projects. Maybe in future releases of JIRA programmers can add this kind of feature. 

Thanks. 

[Ganesh Babu]

Hi @Alik 

If that is the case then you need to have a separate workflow configured to your project which will allow you to make changes to the workflow.

But there are lot of things to remember it will not allow you to create a new status, it only allows you to create a new status only when the workflow is a simplified workflow.

And even being a project admin, a project admin cannot add any transition parameters like conditions, validators, properties, postfunctions. Extended Project Admin permission is only available on the server but not on the cloud variant.

So this permission is made available in order to make a bit less overhead for the jira admins.

[Alik]

@Ganesh Babu 

Thanks for important information. I will take that into account.

Regards

Alik