Request type issue

[kwlwski]

Hello,

Anyone has the same problem like me? Request type rule was working properly over few years till today. Always when I click this icon I was able to change request type using my automation rule:

But... today when I try to change request type using this icon I am forwarding to this bookmark and then I must to fill 4 steps to change request type...

Something is wrong today with Jira Service Management?

Thanks.

[Christopher Yen]

Looks like the move prompts will appear if the issue types / work item types are not using the same workflow it will ask to map the status but for issue types using the same workflow I can still switch without any prompts

[kwlwski]

my work types use the same workflow, something was changed and I do not know why...

[Alex Schaeffer]

I am facing the same issue since today. Changing the issue type from bug to story is redirecting me now to the "move issue" page, where I have to click through multi pages (on horriblly slow speed) to change something that was done with one click until yesterday.

And yes, the issue stays in the same project as before, so no reason to use the "wizard".

Fun fact: Changing a story to a bug works as before using the dropdown...

Fun fact 2: This happens in Jira of two different companies (independent instances of Jira) since today.

[kwlwski]

Good news that I am not the only one... maybe they will fix it...

[Alex Schaeffer]

Adding screenshots from an English page

[Josiah Khor]

The same thing also started happening in my Jira Service Management project on July 31 2026, we did not change anything and all issue types have had the same workflow and fields. 

I'm certain it is related to Request types (we use the default request types feature) as that is the only field the move issue modal asks us to provide a value for.

[Josiah Khor]

@kwlwski @Alex Schaeffer After raising a ticket with Atlassian Support yesterday this was fixed for my org, and the previous behaviour has returned.

[Dave Mathijs]

Hi @kwlwski Welcome to the Atlassian Community forums!

The reason this is now a 2-step wizard is explained:

Your issues' destination project may have different settings than your source project. Even if they're named the same, issue types may use different workflows and fields. You may lose data when moving issues between projects.

Learn more about migrating issues

Workflows

Changing the request type of a work item may also change the work type of an issue.

Sometimes, a different workflow is associated with another work type and statuses need to be (re-)mapped. Example:

The  Service Request workflow in your destination project uses different statuses than the  Change workflow in your source project. Select which status your issues should be in following the move. The following statuses must be mapped to available statues associated with the target project and issue type.

Fields

Your destination's  Service Request issues may have different field settings than your source project. Update the values for fields in these issues, or select Retain to keep the field's current value.

Component or Version field data is permanently lost, if you move issues between projects. Other incompatible fields will appear empty, even if you choose to retain their values.

Learn more about things to keep in mind when migrating issues

[kwlwski]

@Dave Mathijs I do not change project. I try to change request type in the same project. So what to do in this situation?

[kwlwski]

It was working few years without any changes till today