I publish and migrate the new workflow from the default,why do the statuses change?

Mark Tellier October 30, 2014
altassian.pngThe migration aspect made me think that the default would be migrated to my new workflow. The other users are nervous that I will bring them down if I publish and migrate the new workflow from the default. I guess I don't really know what I am supposed to be doing in this screen and the only issue type that I am concerned with is the Infrastructure Change Management issue type. Why is the status important when migrating.Thanks for your help!!!  Best regards,
Mark  

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 30, 2014

This screen is asking you how to map the status.  

Your old workflow has a status "resolved" in it, and the new one does not.  For any issue in status "resolved", JIRA needs to move it to a status that exists in the new workflow, and it's asking you which one.

The trick on this screen is look at the number of issues affected - there's a lot of "0"s in those blue boxes - that tells you how many issues are going to have their status changed, and you can ignore the lines with 0 on them!

Suggest an answer

Log in or Sign up to answer