Here's the situation: I customized the workflow for a few issue types, like Bugs and Sub tasks. Now I can no longer change them to another issue type after they're created since they're part of a different workflow, it seems even when the issue is in a state that is common to both workflows.
Is there any way around this? Or is it just to say that once you give an issue type a customized workflow, you can never change it's type once created?
I'm afraid I'll have quite a few Bugs marked as Stories, etc. that I will never be able to fix.
If two issue types are configured the same, you can simply edit the issue-type field. If they are not, then Jira needs to validate that swapping types will not require more data or invalidate things. For example, if you have the field "steps to replicate" on Bugs, and marked mandatory, and you have it optional, or even not existing on "story", then Jira needs you to fill it in during the change. "edit" functionality simply doesn't have that. But "move" does.
I'd agree it's not obvious or intuitive, but it is the right approach. The field does hint at it too.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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