Issue was created and is corrupted, can't access it due to null value as current step in workflow

[Wendy Ranone]

On Prem Server: 9.1: New project, a test issue was created and is corrupted, can't access it.

An issue was created in a new project and cannot be accessed.  It has a null (blank) workflow status.  I have tried all the ways to fix the issue that I could find here and google and have not been able to fix or delete the issue.

This issue is not needed and I can't change the workflow scheme of the project to the one created for the project.

I am a full admin in Jira

I have full re-indexed, tried bulk delete (you do not have access error)

, integrity checker gave me this 

We just want to delete this 1 issue and all will be well I think.

Any help is appreciated.

[Tim Perrault]

Hi @Wendy Ranone

You will probably need to delete the issue from the DB. If you look at the ticket the second comment had the user delete the issue from the DB.

Tim

[Wendy Ranone]

I saw that in my research, problem is we are very "rookie" at this and don't want to muck up the db messing around, we have back ups, so that would be first step, but wanted an easy sql to run to find and delete the 1 issue, and let our IT database guy do it, but he doesn't have Jira training, and again, we are very rookie at this....

We have a very small use of Jira/Confluence in our organization, and have not made it a priority to have trained administrators, which are myself and another guy by default (know enough to be dangerous).  They now want to ramp up the use for our system modernization efforts, and basically just created a project before all the pieces were in place properly, if I can get this one issue deleted, then I think they will be good to go with this 1 project while we try and get more qualified people in place to administer Jira going forward.

I have not been able to find the sql to delete a single issue.  Thanks for your response.

[Tim Perrault]

I would honestly open up a support ticket with atlassian. I agree with you that the DB is something to leave alone for the most part, but it looks like to get rid of the ticket you will need to go there.

I'm not a SQL expert so I don't really want to throw out any suggestions, but looking through KB articles here is a select statement that will gather the issues from the project so you can look at them in the DB.

select * from jiraissue where project = (select id from project where pkey='JRA');

The only other thing I can think of is restoring your instance from a previous point in time before the issue was created, but you would probably lose a bunch of work you did.

[Wendy Ranone]

Thanks so much, I think opening a ticket is probably the best option, we would lose all the work they did yesterday in that project if we went backwards.  I know the issue key so hopefully that will make it easy.  Thanks again!