Is there something that needs setup for search for Jira issues with Security set.

Question

I just recently added Issue security to a project, with  Public (any log in user can see) and Private (only reporter,assignee, and project role admin).

I am an admin I can see all tickets. When I set a ticket to either Private or Public, it disapears for the JQL (eg key = key-123). I can go directly to key-123, I can see it, I can edit the fields, I can change the security level. It will not show up in the JQL.

If I remove the security level to none, the ticket shows up in the JQL.

The other odd behavior is, if I search the key, then go edit a field on the ticket, the ticket will magically appear in the search without me pressing anything. If I hit the refresh/search button after it has shown up, the issue disappears again, only shows up if I search for it, edit the issue and wait for the ticket to appear in the search.

Matthew_1v4r3s · Answer

Thanks @Akash Singh , thank you for the response. I am hoping this is a caching issue. If I make myself the assignee (or edit any field) the issue will show up in the search, but the second I try to re-search it or  refresh the page, I get no results found.  I been able to repeat this process.

Another note is I was doing this in the sandbox that I had just refreshed a few days ago.
I took the same permission and security scheme to a test project on the prod site and it seems to behaving correctly.  I am starting to assume the sandbox doesn't really index to test this properly.

Akash Singh_vujl0e · Answer

@Matthew From a permissions perspective, you should be able to see all relevant issues as long as you are included in the issue security level. This is evident since you’re able to open the issue when the security level is applied.

My assumption is that this behavior is likely caused by server-side caching. JQL search results can be cached before querying the database, which may result in stale data being returned when you run the same search repeatedly.

If this is the case, the issue should resolve itself once the cache expires. However, if the problem continues even after some time, I would recommend reaching out to Atlassian Support for further investigation and assistance.