We are on  v8.3.1#803002 and still get this error message.

Hello luisc6! I missed mentioning that the Cloud version of this request is JRACLOUD-33054. Please share the steps to reproduce there!

Best regards,
René Chiquete - JAC Champion.

To add ore specifics, we are seeing this on Jira cloud and not a EOL version at all. None of the suggested fixes work.

Hello everyone! We have been analyzing this request, with the following points worth mentioning:

• The message reported is expected when editing an issue. This bug request is about the message "Some issue types are unavailable due to incompatible field configuration and/or workflow associations" appearing in the create issue screen, the message showing in the Edit screen is expected.
• There is a KB in which there are workarounds mentioned in case you want to remove this message from showing in the create issue screen: Some issue types are unavailable due to incompatible field configuration and/or workflow associations.
• For those who are experiencing any problem other than the message showing in the create issue screen, I suggest you reach out to our support team, for them to evaluate and suggest the next steps.
  • Please note that this bug is for Jira Server. If you are experiencing this in Jira Cloud, please raise you request for the Jira Cloud support team, as they are different products, supported by different teams.
  • For Jira Server, in case you are using a supported version (currently Jira 7.3 or newer) and if you are experiencing any other functions not working, please reach out to Support team as well. For versions that have reached EOL (Jira 7.2 or earlier) they are no longer supported and we suggest you upgrade to a supported version to be able for our support team to assist you.
• Since all the confirmed versions so far for this issue have been in EOL versions, and we are not able to reproduce in Jira 7.12.3, we will proceed to close this request, for now, and re-evaluate in case we are able to confirm the issue still exists in any newer versions, which will be confirmed by our support team.

Best regards,
René Chiquete - JAC Champion

I have the same issue. My jira version is 7.0.8, when this  bug can be fixed?

Can we please have this bug fixed already?

The message is shown on Edit page when the issue type is sub-task. All work round doesn't work. When this bug can be fixed?

I have the same issue as @Kristina Mason. Running cloud version, it does not stop me from doing any work but it does show on every create and edit screen.

I'm having the same issue, but it doesn't stop me from doing anything. I can raise all issue types and move them between types. It just seems to show for no reason.

Hi,

I have just created an Agile/scrum project and trying move the tasks from another board into this new project.

That old project has subtasks.

when I created this project, under issue types in settings I had already chosen an option to create sub-tasks when required.

but now when I go to create it... it wont show up in the drop down and put the error as shown below.

You can check if you are affected by this bug using groovy script:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.fields.rest.FieldHtmlFactoryImpl
FieldHtmlFactoryImpl fieldHtmlFactory = ComponentAccessor.getComponentOfType(FieldHtmlFactoryImpl.class)
fieldHtmlFactory.DISPLAY_PARAMS

check output for attribute "restrictedSelection"

[noHeader:true, restrictedSelection:true, theme:aui, isLastField:true, isFirstField:true]

and remove with script - no restart required:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.fields.rest.FieldHtmlFactoryImpl
FieldHtmlFactoryImpl fieldHtmlFactory = ComponentAccessor.getComponentOfType(FieldHtmlFactoryImpl.class)
fieldHtmlFactory.DISPLAY_PARAMS.remove("restrictedSelection")

This is still occuring in JIRA 7.3.x - we used a work around in JIRA 7.1.x but not clear if that will still work.  Can this get fixed soon?

This also appears in my instance and it's very confusing.

This error message also shows up on all of my create issue workflows across our cloud instances of JIRA.

It would be nice to get this fixed, it's incredibly confusing for users.

Hi Barnali.Putatunda481493752,

This is currently in our short-term backlog, so it is something we hope to be able to schedule soon, as we finish work on other higher priority issues in progress. Please do watch the issue for updated, we will update its status as soon as more information can be shared on its progress.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

Hi Team,

Can you please let us know when can we expect this to be fixed.

Regards,
Barnali

Hey kimwall

Please proceed to provide us with the backup so when can have a clear distinct steps on how to reproduce this error. dsantos will provide you a link on where you can upload your backup. Thank you very much!

Cheers,
Azfar

@Kathryn, I'd be happy to help with this. I have an issue open in the support portal JSP-235375 and Daniel referred me to this issue as a result. If you're looking to try and reproduce it perhaps a backup of our environment would help?

Kim

Hello derek_sheeman,

I'm working on trying to reproduce this problem in our systems, and this particular report doesn't have steps to reproduce this initial error message: "Some issue types are unavailable due to incompatible field configuration and/or workflow associations" on the Create Issue screen. I've been working on coming up with the steps to produce the error from scratch, but I noticed that since you have regularly experienced this problem, you might could help me. Since that's the case, would you mind giving some steps to produce the error, and how it presents in your systems? Any input that you could provide would be especially helpful.

Thanks!

Kathryn | Atlassian

This error message shows up on all of my create issue workflows across two different instances of JIRA.
The only way provided to suppress it is yet another edit to a file that is not in the jira home directory
https://confluence.atlassian.com/pages/viewpage.action?pageId=314449378
So yet another file that needs to be updated with every upgrade.

This error message is not helpful, it makes it look like something is broken when it is not.
Please remove it from the Create screen, expecting all issues to have the same schemes and workflow is simply ignorant.

It would be nice if the error could be fixed soon, because it is confusing our customers and tickets are opened regularly.