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 has changed


When we change an issue type, historically this would be completed on the same page as the issue (click on the issue type, click on the type to change to).

Recently without any changes to our configuration, we now find that we have to complete a 3 step "wizard" like process to make the same change - this is done starting with the page "MoveIssue!default.jspa"

We notice that changing from a "Bug" to an "Enhancement" causes this to happen, but from an "Enhancement" to a "Bug" this does not happen.

Can someone advise whether this is the result of a code change in JIRA, and if so how would we ensure our field types are all configured so that this does not happen?

1 answer

1 accepted

3 votes
Answer accepted

It has always worked this way but the rules that trigger it may have changed in Cloud.

The issue type can only be directly edited if the configuration for the source and target issue type is the same - that used to be that both issue types are set to use the same workflow, custom fields and field configuration.  If they are different, then you have to go through a migration, as you've seen. 

ow it's a bit more clever and looks a bit more closely at the fields - you seeing the change from Bug to Enhancement become a migration but not in the other direction implies that there's probably a field for bug that isn't (visible) on enhancement.  The migration therefore wants to check and tell you that you'll be losing that data, but going in the other direction doesn't need migration because you won't be losing anything or have to fill in the field.

So my best guess is that one of your admins has changed one of the issue types so that they're no longer using the same setup.

I mention a rule change because it might also be that Atlassian have changed the rules from fields and workflows to something else which has started to catch your case now.

Jack Community Leader Mar 02, 2021

Note too that the method has changed in the new issue view which we will all be relegated to this month. In the NIV you click on the type icon.


@Nic Brough _Adaptavist_ thanks.  I don't believe any admin made a change, but it helps to know to look for hidden fields on enhancement.

@Jack thanks.  We're already using the new issue view - your screenshot shows what I'd tried to describe a little more clearly!


Thanks both for your help.


I had the same problem and have been trying to find a solution for it. Didnt find any solution but i found this:

Seems to be a bug in JIRA Cloud:

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Bitbucket Smart Commits vs. Genius Commits - What's the difference?

If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...

130 views 0 2
Read article

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