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.
×Hi
we have around 50 projects in Jira cloud and now I would like to change the workflowshemes of all projects. I won't reasign the new sheme project by project. I searched for a solution or add-on here in the community but I didn't find any helpful article.
The recommended Add-On in these community post is not available yet.
https://community.atlassian.com/t5/Jira-questions/Bulk-Change-Workflow-to-all-projects/qaq-p/108277
So it would be nice if someone could help or had an Idea to solve these problem.
Thanks and Kind Regards
Stephan Meyer
If you need to change 50 project workflow schemes then it means that they are similair in all projects. If it is the case, then you should use the same workflow scheme for all projects.
If so, then make a new workflow scheme and assign it to all projects instead of the old ones. It will be the best solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with you, that is exactly what I want to do now.
But I would like to do it with a bulk change function not manualy for each Project.
Do you have a idea for that?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Stephan,
There is no bulk update method that you can use to update all of the projects. You will have to touch each one and make the change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's not something you can automate either - Jira needs to check the configuration for every single change of workflow.
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.
Hi Brant Thank you.
so I'll touch each Project and make the changes
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.
Hi Alexey, thanks for your fast reply
in the past or projectmanagers designed workflows by themselfes and asigned These workflows to a project specific workflow sheme and subsequently to the project. So we havea little chaos till today .
Now all Project leaders together agree to one standard workflow in one standard workflow sheme. And these one and only workflow sheme I would like to asign to all projects now.
Is there a jira function available to do these or maybe a Add-On
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Stephan,
Is the old workflow scheme being used by any other projects? If not and only those 50 are using it. I would do the following:
If you have more projects using the scheme and you have to apply it to all 50 projects you will have to touch each project to make the change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But this does not work if you need to delete a status or if you just want to rename the schema. That is only allowed on inactive schemes, which leaves you making a copy and applying it to each project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This (renaming workflow schemas and removing a status in workflows is only possible for inactive workflows) shows how crappy Jira administration still is after more than a decade with the existing construct of workflows and schemas.
The inconsistent user interface and different behavior when saving changes on different administration pages underlines the need for refactoring in many places.
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.