Some issue types are unavailable due to incompatible field configuration and/or workflow associations.

Hello all,

I am getting the

"Some issue types are unavailable due to incompatible field configuration and/or workflow associations." message when I create an Issue. However everything works perfect, I do not have any problem when creating/editing an issue, even when I created a new custom issue type.

Is there any way to remove this message?

Thx in advance

4 answers

1 accepted

As Nic posted, the warning message is proper one which meant some of your issue types have different workflows configured. So issuetypes which fall under same workflow, they are visible in the select list.

You can simply ignore it as yourself telling that it is not stoping your work.

There is absolutely no reason that I can identify that this message should appear on the create screen. If fact, the statement is completely false as all issue types are available at the time of creating.  It is during editing that this may or may not be true.

On the create screen, it is misleading and unhelpful.

On the create screen, it only appears when you've started to enter data that *might* be lost if you change the issue type at that point. Which would aggravate the users if they aren't told.

I'm assuming that default values for fields also count as "started to enter data." It doesn't change the fact that the line of text "Some issue types are unavailable due to incompatible field configuration and/or workflow associations." on the create screen is patently false. In fact, I get this line for projects which only have one issue type associated to it.

0 votes

It's warning you that there are issue types you can't change to using the type as a field.

The simple way to be rid of it is to remove the issue type field from the create and edit screens. Or, you could configure your issue types in the project to all work the same (although I doubt that's useful to you, most people have very good reasons to make them different). Otherwise, you're into coding.

Which does encourage your users to bother your admins saying "why can't I change to type X"? I'd very strongly recommend NOT implementing that.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,866 views 12 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot