When we do a workflow migration, from 1 scheme to another, why does it ask about migrating issues types that are not even associated with the project's issue type scheme? We have about 100 issue types and every time I migrate, I have to go through all of them to indicate what to do with them - but, the project has an issue type scheme of usually 10 or less and there are obviously no issues of that type in the project (since you cannot if you switch issue type schemes).
Seems very odd to require that...
I reckon this is because you can associate workflows to specific issue types in a workflow scheme. By default, it would be Unassigned Issue Types; this happens when you are changing from a workflow scheme that has workflows associated to the Bug and New Feature issue types to a workflow scheme that has workflows linked with Task and Bug issue types. The Bug issue types would be linked correctly, but JIRA would warn you of potential issues when migrating issues of type New Feature to Task.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
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