Issue stuck in invalid state and cannot be moved

An existing issue was mistakenly moved from a Defect type to Epic. The Defect and Epic workflows share some workflow statuses, but also have ones that are not in common. The moved issue somehow managed to retain its old status, "Ready to Build", which does not exist in the Epic workflow, so now we have an issue that is an Epic, but is not in any valid workflow status. We are unable to move the issue to another type, as we just get the error:

There are errors associated with issues that are to be migrated to the new workflow association.

These errors must be corrected before the workflow association can be completed.

No changes have beenmade to the database.

Errors:

  • The issue XXX-2222 is incorrectly associated with the status 'Ready to Build'

Can this be forcibly fixed by DB manipulation? The current working solution is to clone and continue work on that ticket, but the original will float around forever. Is there anything we can do to correct this?

2 answers

1 accepted

0 votes
Accepted answer

Hi Nancy,

You could try the following:

  1. add the not existing status to the Epic workflow.
  2. move the faulty Epic back to Defect
  3. remove the status from the Epic workflow.

Best regards,

Peter

Peter, I was hoping to avoid having to do this, but this does indeed work!

A few things to note: Adding the status to a workflow isn't hard, and it doesn't matter if there are transitions for it or not. This allowed the issue to be moved back to Defect.

However, removing the status afterward was a bit tricky, since JIRA does not allow you to remove a status from an active workflow. Remember to create a workflow backup before adding the status, as it allows you to point all your workflow schemes to it afterwards.

0 votes

Try the integrity checker first - that has some functions that can fix workflow states. Under Admin -> Troubleshooting (it does other checks, does no harm to run them all)

Hi Nic, I forgot to mention that I tried the Integrity Checker already, and that it just errors out with a Proxy Error.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,318 views 12 19
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