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

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

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
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,971 views 19 22
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you