Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

I get the error There are no issue types with compatible field configuration and/or workflow associa

Oz Shorer
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 13, 2021

Hi, in one of the projects in my company when we move tickets to some statuses I get the error:

There are no issue types with compatible field configuration and/or workflow associations.
The issue type can only be changed by moving this issue.
jira2.JPGDoes someone encounter such an issue and know how to solve it?

1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 13, 2021

This sounds like you have tried to add some form of "change issue type" function to the workflow.

It's failing because the source issue type and the target issue type are not configured identically.

This is not something you should try to do in a workflow, it says you've got a broken process, I would strongly recommend a review of the process with a view to doing it properly.

Garden16_ February 2, 2022

I have a custom type issue types. when I click on the edit button for the custom issue type ,I am getting this message. All the work flow, field config screen and screen schemes are independent. Don't know how to  get rid  of this issue 

There are no issue types with compatible field configuration and/or workflow associations.
The issue type can only be changed by moving this issue.
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 2, 2022

Er, yes.

You say "All the work flow, field config screen and screen schemes are independent" - that's the whole point of the message.

It's failing because the source issue type and the target issue type are not configured identically.

It's telling you that you can't edit unless the field configuration and workflows are the same.

Garden16_ February 2, 2022

 It's failing because the source issue type and the target issue type are not configured identically. - what does this mean .

How can I configure it. Please advise.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 2, 2022

I don't know how else to say "the source and target types are not configured the same" - it means exactly what it says.  To "fix" this, configure the two issue types to work the same way.

Garden16_ February 2, 2022

I have Bug Issue type and subtask associated called defect

Bug issue type has its own work flow screens and screen scheme and Field configurations, work flow and work flow scheme

Defect subtask issue type has its own has its own work flow, screens and screen scheme and Field configurations

Then there are other issue types like epic, stories, Pre condition, etc that have the Project default configuration , scrum default screens, scrum default screen schemes. default field configurations ,work flow and work flow scheme

In the issue type screen scheme I have 3 screen types mapped  based on the issue types

Bug mapped to bug issue type screen scheme 

defect mapped to  defect issue type screen scheme

both  Bug and defect are mapped to  ' Bug& defect field configuration '

rest of the issue types are mapped to  'Default field confutation'

Both field configurations are mapped to scrum Project's field configuration scheme.

 

I would want them to  have different screen schemes and screens and work  flow.

To "fix" this, configure the two issue types to work the same way. I do not want them to be the same .

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 2, 2022

> I do not want them to be the same 

Ok, then you are going to have to use "move" when you want to change the issue type, as the error message states.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events