Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-5254

Change workflow scheme for multiple project at the same time

    • 16
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      When modifying a workflow that is currently used by a workflow scheme configured for multiple projects, we must unset the workflow scheme to all project, modify the workflow, then set it pack. When there is a lot of project with a lot of issues, this is a long task.

      It would be a good thing if we can edit a workflow (adding a new function, condition, step, transition, etc...) then when done, all project using the workflow are notified and all association are done one time, for all project using this workflow.

            [JRASERVER-5254] Change workflow scheme for multiple project at the same time

            Hi, great script here (SR + console) : https://community.atlassian.com/t5/Jira-questions/Bulk-update-workflow-Issuetype-Screen-Scheme-for-multiple/qaq-p/2104218
            for those like who were looking for a solution to this (requires the Scriptrunner addon tho).

            Sylvain Leduc added a comment - Hi, great script here (SR + console) : https://community.atlassian.com/t5/Jira-questions/Bulk-update-workflow-Issuetype-Screen-Scheme-for-multiple/qaq-p/2104218 for those like who were looking for a solution to this (requires the Scriptrunner addon tho).

            Suggestion created 20 years ago. Suggestion refused 10 years later. Another 10 years later the problem still persists. That's the spirit of Atlassian team, where can I sign the contract?

            Christian Joel added a comment - Suggestion created 20 years ago. Suggestion refused 10 years later. Another 10 years later the problem still persists. That's the spirit of Atlassian team, where can I sign the contract?

            There are tons of such issues opened all over the internet and there are scattered. For example this: https://community.atlassian.com/t5/JIRA-questions/Bulk-Change-Workflow-to-all-projects/qaq-p/108277 . They are always "rejected" by Atlassian and I have no clue why.

             

            This is so important functionality especially if you have a lot of projects (1000+). How I am supposed to do a mass migration (if I need to)? By hand? Issue Type Schemes for example has such functionality and the "core idea" is there. All it needs is a GUI or "for all projects do...." like story.

             

            I checked the REST APIs as well. Nothing is there. Is there any workaround on this matter?

            Nikola Rezachev added a comment - There are tons of such issues opened all over the internet and there are scattered. For example this: https://community.atlassian.com/t5/JIRA-questions/Bulk-Change-Workflow-to-all-projects/qaq-p/108277  . They are always "rejected" by Atlassian and I have no clue why.   This is so important functionality especially if you have a lot of projects (1000+). How I am supposed to do a mass migration (if I need to)? By hand? Issue Type Schemes for example has such functionality and the "core idea" is there. All it needs is a GUI or "for all projects do...." like story.   I checked the REST APIs as well. Nothing is there. Is there any workaround on this matter?

            If you change a workflow map in the middle of a project from 'Default' to a custom workflow, will it have a negative effect on the calls that exist in the project before you made that change? Will it delete them, for example?

            Susan Rossney added a comment - If you change a workflow map in the middle of a project from 'Default' to a custom workflow, will it have a negative effect on the calls that exist in the project before you made that change? Will it delete them, for example?

            jlee7 - your best bet is to write what your trying to do as a question on https://answers.atlassian.com. The community will be able to help you out and point you in the right direction.

            Josh Devenny added a comment - jlee7 - your best bet is to write what your trying to do as a question on https://answers.atlassian.com . The community will be able to help you out and point you in the right direction.

            John Lee added a comment -

            jdevenny or anyone else – Can you point me in the right direction in getting Script Runner to make a bulk change? I have a similar situation as jhult

            John Lee added a comment - jdevenny or anyone else – Can you point me in the right direction in getting Script Runner to make a bulk change? I have a similar situation as jhult

            There's no native functionality to do that type of bulk change.

            If you're running a self hosted instance of JIRA, I'd take a look at the Script Runner plugin.

            Josh Devenny added a comment - There's no native functionality to do that type of bulk change. If you're running a self hosted instance of JIRA, I'd take a look at the Script Runner plugin.

            Aha! I was trying to mass change the workflow schemes (to one workflow scheme) for projects which currently have different workflow schemes set. Is there a JIRA issue for this functionality?

            Jonathan Hult added a comment - Aha! I was trying to mass change the workflow schemes (to one workflow scheme) for projects which currently have different workflow schemes set. Is there a JIRA issue for this functionality?

            Try doing this:

            • Go to the workflow schemes page in global admin at [INSTANCE URL]/secure/admin/ViewWorkflowSchemes.jspa
            • Click edit on the workflow scheme that you want to change
            • Check that there is a green lozenge at the top of the page that says "Shared by X projects" (otherwise the scheme isn't shared**)
            • Make changes to the workflow -> issue type associations
            • When you click publish, you'll be taken through a migration wizard and the migration will be performed for all projects that use that scheme.

            **In order to change it for multiple projects, you need to make sure that the scheme is actually used by multiple projects. In order to do this, go to each projects "Workflows" tab and select "Switch scheme". This will take you through a process of choosing a new scheme - make sure you choose the same scheme for the projects you want to share the scheme between. Once this is done, the above steps will work.

            Josh

            Josh Devenny added a comment - Try doing this: Go to the workflow schemes page in global admin at [INSTANCE URL] /secure/admin/ViewWorkflowSchemes.jspa Click edit on the workflow scheme that you want to change Check that there is a green lozenge at the top of the page that says "Shared by X projects" (otherwise the scheme isn't shared**) Make changes to the workflow -> issue type associations When you click publish, you'll be taken through a migration wizard and the migration will be performed for all projects that use that scheme. **In order to change it for multiple projects, you need to make sure that the scheme is actually used by multiple projects. In order to do this, go to each projects "Workflows" tab and select "Switch scheme". This will take you through a process of choosing a new scheme - make sure you choose the same scheme for the projects you want to share the scheme between. Once this is done, the above steps will work. Josh

            jdevenny,

            Could you provide exact steps on how to bulk change the workflow scheme for multiple projects?

            I read through the above Confluence documentation but am still missing something.

            Jonathan Hult added a comment - jdevenny , Could you provide exact steps on how to bulk change the workflow scheme for multiple projects? I read through the above Confluence documentation but am still missing something.

              Unassigned Unassigned
              4faf22ce9015 Pierre Fortin
              Votes:
              170 Vote for this issue
              Watchers:
              100 Start watching this issue

                Created:
                Updated:
                Resolved: