I've read through the discussion on page https://community.atlassian.com/t5/Jira-questions/How-do-I-use-a-different-workflow-on-an-issue-than-the-project/qaq-p/394295 regarding to different Workflow assignment. But that isn't the same questions I am asking here.
1. I'd like to assign different Workflows based Component as well even for same type of the issue. Is it possible?
2. Also, once an issue is created, can this issue's Workflows be changed to different Workflows? The page I mentioned above has the words about remapping status. So, sounds like this feature is supported, but I haven't seen the effect.
Thanks a lot
Hello @A L you can only have different workflows if you have different issue types, each issue type can only have one workflow assosiated to it, what you could do is to have within the same workflow multiple transitions between statuses and each one would have a condition based on the component value. That way you achieve different processes within the same workflow, anyway this won't be easy to maintain or to understand the process for the users either, which is why I wouldn't recommend it yet it would meet the needs.
About question 2 to change the workflow you must change the issue type by using the move option in Jira which will ask you for mapping statuses as part of the process in case one of the statuses aren't on the other workflow.
I hope that is clear enough for you.
1. No. Workflow can be associated to an issue type. It's not possible to use different workflow for the a single issue type based on the Components.
2. You can add a new workflow to the workflow scheme and associate with the issue type. It'll move all the existing issues from old workflow to new workflow while changing the workflows. You may refer to Configuring workflow schemes for more details.
Hi @A L
For (1), you can only set workflows per issue type - however, you could customise a workflow to vary depending on a field's value.
You could do this by using conditions - for example:
Here I can assign various conditions - such as:
^ This way, you could have one workflow but different steps depending on the value in the component field. It's not an ideal solution but - depends on the use case :).
You'd need to be careful though, as removing the component could end up with an issue being "stuck" in a transition, so I would suggest having a way out as a fail safe (eg. all users can transition all issues back to "To Do" from any status).
For more information on advanced workflow config, see this page.
For (2), as @Veera mentions you can change a workflow post-issue creation. You can:
If you remove the status your issue is currently in, it will ask you during implementation of the new workflow which status you want to move those to.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events