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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try to run Lock JIRA and rebuild index
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you set security level on that issue ? Probably the other user access is denied by the Issue Security Scheme of the project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.