The issue you are trying to view does not exist

Hi,
When someone tries to access an issue which was created in JIRA
they get an error that the issue does not exist but an filter on an dashboard shows that the issue exists.

Can someone shed some light.

9 answers

This widget could not be displayed.

Did you set security level on that issue ? Probably the other user access is denied by the Issue Security Scheme of the project.

This widget could not be displayed.

Thank you for Quick response Boris.

As an system admin I myself cannot access that issue.

This widget could not be displayed.

Being an admin does not mean you bypass the issue security - you need to check what the scheme says.

However, secured issues should not appear in searches, so my instinct is that your index is damaged.  Try re-indexing the project to start with.

This widget could not be displayed.

Thank you Nic, I have checked that as well and there is no Issue Security Scheme applied. I have re-indexed the instance just about a day ago.

 

This widget could not be displayed.

What Nic says makes a lot of sense, so try running a re-index on one of the projects which contains issues that has this behaviour, and see if it fixes the problem.

This widget could not be displayed.

Try to run Lock JIRA and rebuild index

This widget could not be displayed.

The version we are on is 5.2.11 which I dont believe has that option. But we are soon upgrading to 6.4.12.

This widget could not be displayed.

An upgrade will re-index as part of the process.

But you can still re-index JIRA - later versions have "re-index in background" and "re-index project" options, but all versions have the option for a full re-index

This widget could not be displayed.

We tried re-indexing the project and it didn't work. A full instance re-index (we specially used the background re-index) did the trick. Would that this could be cron'd out or better not an issue at all.

Makes sense - a project re-index runs through existing issues in the project and builds the indices for them.  It doesn't look at deletes or linked stuff like a full reindex does.

I know there's an instinct to reach for a regular re-index, but this is actually a really bad idea.  A broken index is screaming "something is corrupting the index" and you should be fixing that, not plastering over the crack and pretending it's all ok.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

275 views 1 3
Join discussion

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