Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Associate different Issue type in same schema error


I’m having a very unusual issue

Current implementation

  • Created 2 different types of issues that can be raised by users
  • Defined different screens to capture these details
  • 1st Issue type is already associated with WF (WF1) and its running fine.


  • When I assign the 2nd issue type to its workflow (WF2) and publish I get error messages

MSG details

Step 1 of 2: The current status of each issue needs to be changed so that it is compatible with the new workflows.


Notes / Obeservation

- Its trying to link WF2 to WF1 – Not sure why…

- Both these workflows are in WF same schema… should they be different?



2 answers

I had a project in the project trash that also used the same workflow scheme. After removing it immediately instead of waiting for 60 days the migration of the issues from the old workflow to the new workflow was executed without an error message. No longer "The current status of each issue needs to be changed so that it is compatible with the new workflows."

So, perhaps check if there are no projects in the trash using the same workflow scheme.

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 21, 2020

It is not "trying to link wf2 to wf1", it is trying to migrate the data.

Imagine you currently have a single workflow in your scheme mapped to all issues by default (or even explicitly saying Bug: wf1, and Feature: wf1)

wf1:  Open -> in progress -> done

Now imagine you create 6 issues, three Bugs, and three Feautures, progressing some of them through their flows, so you now have a Bug and a Feature in each status.

Now create:

wf2:  New -> in progress -> closed

Then associate that new workflow with Bugs.  Jira needs you to tell it what status the Bugs should be in in their new workflow.  The Bug workflow does not have "Open" or "done", so you are going to have to migrate two of your existing Bugs to fit with New and Closed.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events