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?
Basically, if you want to configure a workflow scheme that is shared by more than one project, you will need to do one of the following:
I believe that the second option - to copy the entire workflow scheme, associate the new workflow, and then associate the copy with the project - is the best option in this situation, as it won't force you to change the status unless the status available in the new workflow are different then the ones from the old workflow. Regarding your last question, there can only be one Workflow Scheme active per Project. You can have different Workflow Schemes active for different projects.
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