Stuck in a status

[Audra Bonacki]

Hi there, we have a ticket that was created at a time when our server went down. It is now stuck in the status in which is was created and cannot move through the rest of the workflow. As an Admin, I don't see a way for me to even close it on their behalf. We don't want to delete the ticket as there are Subtasks and comments attached to it. Any ideas? Thanks!

[Audra Bonacki]

Hi everyone, thank you for your suggestions. I ran the integrity checker and that fixed the issue!!

[Matt Doar]

You can also move the one issue to a new project/issuetype that uses a different workflow. Then change it back to the original project and workflow. Annoying!

[Dave Liao]

Thank you! Even five years later, this is necessary sometimes.

Usually when I run into this issue, I run the Integrity Checker and fix any workflow-related issues found.

This time, I had tickets that were stuck in a strange status, even after running Integrity Checker. Moving the issues to a different issue type (that happened to be mapped to the same workflow) and then back to the original issue type solved my problem.

[Juan Manuel Ibarra]

Hi! You can use the database intgrity checker 

Choose System. 

Select Troubleshooting and Support > Integrity Checker to open the Integrity Checker page.

The integrity checker has a number of 'integrity checks' that look for common inconsistencies in JIRA's stored data.

The "Check workflow integrity" option must resolve your problem.

For more information:

https://confluence.atlassian.com/adminjiraserver071/using-the-database-integrity-checker-802592958.html

Regards!
 

[Nic Brough -Adaptavist-]

Try running the integrity checker (log in as admin and use the admin search to find it)

This is a symptom of having an issue that has a status that does not match its workflow in the database, which can happen if it crashes.