Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Change issue type goes to Move

If I click on the issue type and want to change it, e.g. task -> bug, then it used to just change it right away. This was very quick and easy to use.

But since about a week ago changing the issue type brings me to build move page where I have to change the type again and go through a 3-step process just to do this. It is very annoying and results in no-one changing issue types anymore.

Does anyone else have the same problem, and if so knows how to revert back to the old in-place changing?

We are using the next-gen board.

5 answers

5 votes


It means that either workflow or field configuration or screen configuration is not the same for bugs and tasks anymore.

Hmmm... I am using the next-gen project (or what it is called) and there is no workflow configuration or similar. I only have a page where I can specify issue types and it looks like below. I can't really find any setting similar to what you are describing... 

Also, this just started happen out of the blue without any changes from our side to the issue settings,

Any ideas?



1 vote

Hello everyone,

Thank you all for reaching out to Community!

I would like to share some updates regarding this issue.

The question was posted in August 2019 and at that time there was a bug regarding next-gen projects and it was fixed, that why it started working for Fredrik again.

This issue started happening again and it was reported as a new bug:

Please, click on “This affects my team”, so our dev team can be aware that your site is affected by the bug and also watch to receive future updates.

Kind regards,

Hello @AN 

Thank you for the clarification.

Please clarify why the task in JIRA has low priority?

The priority of the bugs increases based on affected customers and currently, only 5 reported this issue.

Also, it will be based on impact, but it was already escalated internally and soon it should have an update.

For more information, please check our policy below:

I added the link to this question as an internal comment, but feel free to add a comment on the ticket where our dev team will receive a notification.

Fredrik, did you ever figure out the cause for the difference in behavior? I'm experiencing the exact same problem.


In your video, Alexey's answer is why.  Your issue types are configured differently.

It suddenly just changed back to the original behavior for us. We never did any changes (the reply by Alexei was not applicable) so I just assume it was something that got patched.

It was definitely very annoying and I hope you can get it working again.

Nic, can you clarify what you mean by "Alexey's answer is why"?

I have no workflow configurations, and I can change the issue type seamlessly between Seed and Story despite the screen configurations being different between those two issue types. Furthermore Story and Bug have the same screen configurations.

See comparison among the three issue types at  

Just want to add in that this also suddenly started happening to us out of the blue. We're not using Next-Gen but Classic boards on Jira Cloud. So weird.

There is probably something with the latest update, my team told me that they have the same problem since the beginning of the month.

We can change from issue type 1 to 2 but to issue type 3 and 4, the move issue workflow is used instead of quick change.

The issue types are configured differently, so you need to move instead of just edit.

It's not a problem or even an issue, you've set it up to such that it has to work this way.

That just doesn't make any sense considering it's been running fine with no issues for like 9 months (where we moved to jira) and then suddenly with no changes, this happens.

Like Karim Kuchkarov likes this

One of your admins has changed something.  We can't tell you any more than that, we're not your admins.

Or a change was deployed that changed the behaviour. Not to say that it isn't a change on our side (it could be), but simply stating that it can only be something we did might be a bit too square ;)

Like # people like this

@Nic Brough _Adaptavist_ looks like you didn't even try to test the problem.

I have the same problem as described by the guys above.

I can easily change the task type from "Bug" to "Task", but vice versa "Task" to "Bug" it redirects me to this "Move" screen

Below is a screenshot with the fact that I have the same fields for both issue types and issue types are configured in the same way


So please NOW explain to us what is the problem and how can we solve this?

Please do not pretend that there is no problem when several people signal to you that there is one.

I have tested, that lead me to the answer given above that it seems you have not managed to see.

@Nic Brough _Adaptavist_ it looks like you are not reading it carefully.

In all the comments here, users wrote that no one has made any changes either with the field configurations or with the workflow, and everyone has the same problem. And all the comments end up with that the problem not being resolved.

But with perseverance, you continue to repeat the same thing that we've made some changes in settings.

What does your "community leader" badge mean? does that mean you give bot answers? 

Any real people here who can solve such a problem?

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you