Issue type is a structural thing, and changing it is not trivial. It can only be done easily if the old and new issue types are configured identically.
I'd question the desire to change the issue type as a matter of course. It suggests a broken process rather than a useful step. Are your users routinely raising the wrong type all the time?
Yes. Users routinely raising the wrong type all the time?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you have script runner, you can write a script in the post function of workflow. There you need to refer to java APIs and move the issue to same project & another issue type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I found that there is a way by adding a Script post function method > Clones an issue, and links.
But this way a new ticket will create and the old ticket still exists.
https://confluence.atlassian.com/adminjiracloud/advanced-workflow-configuration-776636620.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.