Updating issue type on a classic project?

[Deleted user]

I have two classic projects set up. When updating an issue type, on one project I'm able to update at the Issue type icon.  On the other it get an error message saying "you cannot update the issue type in this project".  For this project we are required to use the Move functionality to move the issue type from one to another which is a lot of extra steps.

[Petter Gonçalves · Accepted solution]

Hello @[deleted]

Thank you for reaching out.

Per your description, I understand that you can simply click in the issue type drop-down to change the issue type for a specific issue, however, for some other projects, it is not possible and requires you to follow the move issue client, which have way more steps to be filled. Is that correct?

Please, allow me to clarify what are the details that cause both scenarios:

1 - If you are using a classic project and all your issue types are using the same workflow under Project settings > Workflows, you will be able to easily change your issue types without filling any other steps.

2 - If you are using a classic project and your issue types are using different workflows under project settings > Workflows or you are using a Next-gen project, Jira will require you to use the move issue client to change the issue type on your issues.

The moving issue client operation is required because you must set a new valid workflow status to keep your issue properly mapped when you move it to a different workflow. In next-gen projects, it is used unique entities to define each issue type, so the same process is also applied to it (See JRACLOUD-72790).

That being said, if you want to change your issue types without needing to move your issues, you'll need to set a classic project and configure the same workflow to all the issue types related to that project.

Let us know if you have any questions.

[Deleted user]

Thank you. It's what I suspected but, appreciate the confirmation.