we are seeing exactly the same behaviour.
When tickets are "moved" manually, everything works properly (another workflow is taking over and everything works smoothly). However, when updating Issue Type through automation, the issue type is changing, but the workflow seems to remain the same, so do all the original validations that should not apply to the new issue type.
Is there a way to "properly" move a ticket from one type to another automatically?
Thank you for your reply, @mogavenasan
The workaround technically works, but it introduces a few problems in a context of service management project, for example, in our case, most of the issues are managed via email where request participants respond to an email thread. Creating a new issue would remove that thread dependency and result in a new ticket :(
Unless there is another way to recognize responses to the original issue, that would not work
In order to change the Issue Type via a script or automation, we expect at least the field configuration and workflow is the same. Even with this similarity, you might find something else is broken along the way.
You find a lot of useful information from the following threads:
It's a pretty risky thing to do.
On the other hand, about the workaround that I have pointed, if you want, you can keep the original Jira issue and sync the comments to the new one.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events