nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problems in queries with custom fields - re-indexing

Dinael Silva

I have a problem with my JSM that I don't know the cause.
Inside my project I have a custom field that I fill with the user code in my software. But if I clear this field after being filled in and perform a JQL query filtering by user code, the issue is still returned.

Does anyone know what it can be and how to solve it?
In the telegram group I was told that it would be a reindexing problem, but I can't reindex in the cloud.

Thank you very much in advance.

Accepted answers

Daniel Eads

Hi @Dinael Silva , welcome to the Community!

Jira Cloud makes use of some eventually-consistent caches for search results. A fairly long technical explanation is available here if you're interested in the specifics, but the gist is that repeated searches might not match the reality of the issues right away. In your case, you've run a search (which was then cached), made a change to an issue, and then run the same search again. Instead of the search fully running again, Jira's backend is pulling the cached results from the last time you ran that search moments ago.

There are two ways this will change:

The cache will expire after some period, and your search will be performed again with the correct results this time
You can make some minor, unimportant change to your search that will cause it to look like a different search - resulting in a cache miss and the search being performed (and not pulled from cache)

I hope that helps explain things a bit! You won't have the ability to reindex the system, or need to (as you may in Jira Server for search inconsistency) since what you're seeing is search result caching behavior.

Cheers,
Daniel | Atlassian Support

All comments

Benjamin_tmh9yg

Hi @Dinael Silva ,

This indeed looks like an indexing issue since the search results does not match up. Would recommend contact Atlassian for additional support on re-indexing as this option is not available.

-Ben

Dinael Silva

Hi @Benjamin,
I contacted them, but nothing did. They just got back to me asking to open a question in the community, as the support for free accounts is only in the community and that some Atlassian support engineer or user would answer me.

I was honestly upset. Because I'm using the free account in a pilot test to go up to the entire company.

Can you tell me if there is any other way to get in touch with them?

Cheers
Dinael Silva

Benjamin_tmh9yg

Hi Dinael,

Thanks for the update. Let me see what I can find out.

-Ben

Daniel Eads

Hi @Dinael Silva , welcome to the Community!

There are two ways this will change:

The cache will expire after some period, and your search will be performed again with the correct results this time
You can make some minor, unimportant change to your search that will cause it to look like a different search - resulting in a cache miss and the search being performed (and not pulled from cache)

Cheers,
Daniel | Atlassian Support

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management