When I try to Move Issue from one project to another project ,Step 1 allows to change the project name and issue type. Step 2 is getting skipped and step 3 is shown for updating other fields.
Message is shown as "Step 2 is not required"
Can anyone please suggest how to enable Step 2?
I know this is an old thread, but I was wondering if there is a way to make the process stop at Step 2 as well. I would like to use this step so the users can change the status when moving from one project to another. I know that if the workflows were different, it would force this, but is there anyway when the workflows are the same to allow users to change the status on move?
Very easy - "I want to move an issue as swiftly and easily as possible" is the human version. When you look at it, that gives you a really good guide of "only ask the user for information on the things you cannot do automatically". If a field or status is valid in the new config, then by asking for it, you break the "simplicity" rule.
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...
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