Service Desk: Changing Issue Type via postfunction

Question

Hello,

i want to change the issue type via a postfunction during a transition.

It seems to be possible with the JMWE postfunction "Set field value". In the configuration of the postfunction i can set the the new value to the new issue type.

While testing, the postfunction is working correctly. The Issue Type is changing from "Incident" to "Task".

Unfortunatly, all the Transitions in the workflow seems to be crashed. There are no Transition-Buttons available in the Issue. Obviously there is something going wrong while transforming the workflow.

Does anybody has any ideas?

Thank you for your help

David Fischer · Accepted Answer

Hi Florian,

unfortunately, setting the Issue Type field only works if both source and destination issue types share the same workflow. Otherwise, Jira gets confused.

What you'd need is a "Move Issue" post-function but it's not that simple, as there are many steps involved in moving an issue (see what happens when you use the "Move issue" operation in the UI). And unfortunately there is no "Issue Move" Manager or Service in the Jira API that you could easily use in a Groovy post-function either.

You can Google "jira scriptrunner move issue" for code examples (ScriptRunner code snippets will usually work as is in JMWE, although they can be simplified using JMWE's simplified API) but it looks like none works satisfactorily.

Nic Brough -Adaptavist- · Accepted Answer

Issue type is not really a simple  "field".  It's a structural property of an issue, off which hangs a load of configuration data.

My guess is that you have different workflows for Incident and Task - these hang off the issue type.  So if you just change the issue type without doing all the workflow migration, they will fail, badly.

You should not use this post-function to change the issue type, unless ALL the configuration for the source and target issue types are shared (not even identical, they have to be shared)

Ravi Varma · Accepted Answer

Hi @Florian,

You should give a second thought, if this is your use case.

JIRA allows defining configurations at issue type level, which makes JIRA so flexible and scalable.

Reason for abnormal behaviour - As you have changed the issue type, the workflow associated with the new issue type would come into effect and hence the new transitions and statuses pertaining to the new workflow would be shown. In fact, if there had been a broken validation, JIRA would not have allowed you to change the issue type.

* My recommendation would be to never change the issue type, unless you are aware of the consequences.
* You should be supplementing/realizing your use case by using a custom field.
* If it is imperative to change the issue type, then you have to ensure that the configurations for both issue types are same.

Hope this addresses your concern.

If you feel that this is useful then please accept my answer, which would motivate us take up more community questions.

Regards,

Ravi Varma