Displays incorrect fields for issue type when issue is moved

In a Specific Project on a specific issue type the following happens:

When moving  Issue type A  to Issue Type B , the fields associated with Issue Type C are displayed instead of those for Issue Type B

When Moving Issue type A to any other issue type the screens are correct

I compared all the screens of the 3 issue types and they are significantly Different.

We upgrade from JIRA 5.2.3 to 6.3.5 a week ago.  Could this be the issue? 

Any idea why this might be happening?

1 answer

0 votes

What happens if you try to edit an existing issue of type B?  Does that bring up the correct fields?

Also, what happens if you enter all the data into the "wrong" list of fields and commit the move?

Hi Nic, When editing or Creating issue type B the fields are correct When I enter all the fields and move B to C for instance some fields are missing, but when I edit I still have the option to populate the correct fields that are associated with issue C.

Any Ideas Guys?

So which fields from C are missing from the move screen?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,984 views 19 22
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you