We wanted to include/assign a new workflow created to an existing workflow scheme. To do this, we were told to mark the workflow as ‘inactive’, make the change, and flip it back to ‘active’. While doing this; (a) it reverts all issues in this scheme to Open status (b) it forces people to not use the Application during this time. While we can coordinate with the team to not use the Application, reverting the issue status to the Open status is something that we cannot do for the fact that we will have tons of issues active at any given point. Please suggest a solution, as we will be assigning workflows to an existing workflow scheme in the future as well. Also, please confirm, if there can be only 1 workflow schema active at a given point?
i would suggest creating a copy of your workflow scheme and assigning it to the project (which in result changes nothing, but you have the "original" workflow scheme free for editing). Then assign the workflow you wish to the "original" workflow scheme. As final step, assign the "original" workflow scheme to the project, with the status mapping as desired.
I hope this helps,
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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!
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