Originally asked by Thomas Palludan Hargreaves on 20 September 2023 (original question)
We have two Jira Cloud Service Management Projects and we’ve been trying hard to solve this one but it seems that you cannot currently set an issuetype on a JSM ticket after creation.
We’ve tested the same code for two Software projects and that works, we also tested from JSM to Jira Software and that also seems to work however the problem keeps appearing when we try to change the issuetype after issue creation on a JSM project.
The creation of the issue itself seems to work and for some reason the issuetype mapping also works perfectly in this case but if we go to the issuetype afterwards and change it (note the other issuetype has a different workflow so this corresponds to a Move action within the same project) and the only thing we are trying to synchronize is the issuetype then it simply ignores the issuetype.
We’ve had two teams trying this out independently and we get the same conclusion.
Even if you change something on the issue after the move action in the same project it will not change the issuetype. The Status will be changed as normal and if the workflows are different it will complain about synchronizing status when the issuetype changed.
We tried just setting the issuetype directly to a specific name we knew existed via the incoming sync and it was ignored (other items were synch’ed correctly).
We tried using the issuetype id to set it specifically in the same way. Here we got an error that it couldn’t match the issuetype id’s in the JSM project but we checked and the id’s were correct. We also did the same thing for Jira software and it had no problem using the issuetype id’s or setting them directly. For Jira software it worked both with and without mapping of issues.
I feel like we’ve tried everything so I really need some help here?