Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira 7.5.4 stale filter results

Deleted user Nov 15, 2018

So we've got some Filters set up and are using ScriptRunner:


Filter1: "IssueID1 OR IssueID2 OR IssueID3"

Filter2: issueFunction in subtasksOf("filter =/"Filter1/"")


This had been working fine, I guess? But: I added additional subtasks to IssueID1|2|3 today and it took ~4hrs for the subtasks to show up in Query2. Since my boss has Query2 in his JIRA Dashboard, it's kind of important that these be correct. :-)


I'm assuming there's stale cached filter results stored somewhere, but a reindex didn't help. Any ideas on how I might avoid this going forward?

1 answer

0 votes
Tom Lister Community Leader Nov 17, 2018

Hi @[deleted]

are you displaying in dashboard using filter results gadget?

is it configured to refresh at intervals?

Deleted user Nov 19, 2018


We are using the Filter Results gadget, and the option for "Update every 15 minutes" is unchecked. I guess this is normal then? :-(

With the update option unchecked, what is the typical refresh interval? Can the filter gadget be configured not to use cached results at all?


Dave P

Tom Lister Community Leader Nov 19, 2018


The gadgets are views on a data component under the hood. Once displayed they will not refresh the results unless configured to use a timed refresh cycle.

Similarly your view on an issue won't change if someone else updates it unless you do something that cause a page refresh.

I think this is a common expectation of Jira screens which causes some confusion ;-)

not sure if there are any plugins that would address this. The downside of too many components refreshing is a hit on system performance.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events