Changing issue type via Move option does not request the new request type

[Pierre CARRAZ]

Hello,

We have moved from server instance of JSM to Cloud instance and we have noticed a strange behavior on the Cloud instance.

To change the issue type associated to a ticket, we are using the Move action.

On the server instance, the Move action requests to choose the new issue type and then the new request type linked to the choosen issue type.

On the Cloud instance, the Move action requests to choose the new issue type but does not request to choosse the new request type linked to the choose issue type.

As a consequence, at the end of the Move action, the ticket has the correct issue type but an unknown request type. We have then to modifiy it.

Is that a normel behavior ?

If this is not the case, what can be the cause of this behavior ?

Thanks for your help.

Regards.

Pierre

[Jehan Bhathena · Accepted solution]

Hi @Pierre CARRAZ ,

That is the current behavior, couldn't find any ticket for this that claims this might be a bug.

This article here gives a logical reason to the behavior though https://www.reddit.com/r/jira/comments/15c2r34/comment/jtu7dzc/

[Pierre CARRAZ]

hi @Jehan Bhathena 

Thanks for the reply.

I'm however suprised by the change of behavior beteween the server instance and the Cloud instance.

Regards

[Jehan Bhathena]

For an alternative to auto update the field you can try using Jira Automations, to detect if an issue is transitioned from a certain type, and based on that you can set a default one if needed.

If this thread helped, please can you mark the Answer as Accepted.

[Dwight Holman]

As well as the answer from Jehan, Atlassian have a Labs feature for Company Managed projects to allow a Default Request Type to be associated with each Issue Type.

Check out the documentation for more info:

https://support.atlassian.com/jira-service-management-cloud/docs/choose-default-request-types-for-your-issue-types/