Cannot use an issuetype since software update

I receive the error "Some issue types are unavailable due to incompatible field configuration and/or workflow associations". I cannot find any differences between the problematic issue type and the others except that there is a specific workflow. The assigments look o.k..

1 answer

0 votes

This sounds like you are trying to change an issue type using the simple issue type field.  You can only do that if the source and target issue types both have the same field configurations and context, and the same workflow.

You say the workflow is different, so there's the answer.  You'll need to use the "move issue" function to change the issue type.

Hello Nic, thank you for the quick answer. The Problem occured when I tried to update an issue. I tried to move and then I tried to create a new issue. Neither one did work

I cannot see what is wrong with the workflow. It worked before the last Jira upgrade.

You won't get that sort of error when you move an issue - could you show us exactly where it goes wrong when you use "move"?

Hello Nic, sorry for replying late. As stated in my previous answer, the error occurs when I try to move as well as when I try to create a new issue with this specific type. Attached is the screenshot with the error:

jira_error.png

I'd like to see the move error, not the create.

the create is trying to stop you from losing data already entered (or defaulted) - if you changed to a new issue type with a different config here, it has to lose all entered data.

The move is a different story.

Nic, I believe there is some confusion. The screenshot that I sent was a trial to open a test issue. There is no link to the data, that I cannot edit.

For some reason the system does not allow to work with the specific issue type: no edit, no move no create.

The error messsage suggests to investigate the field configuration and/or workflow association.

That's why I was asking for what you see on move

What happens when you click "move" on the issue?  What is the error message and where is it? 

Actually, you now say you can't move it, so you can't have got an error message, so I'm even more confused.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

36 views 1 5
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