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; } } }

Chart doesn't use the latest data

Judit Gal

Hi, I set up a dashboard setting 30 minutes for how long dashboard data should be considered up to date, and Check the cache every 2 minutes (just to see if this low number will give a better result).

Waited about an hour and the expected data is still not showed up (the latest ticket is still missing).

Earlier we noticed that a ticket which was modified the previous day was missing and we started to investigate. Then I edited the chart to see if I find something there to cause the problem. After saving again the chart the last day data showed up but we noticed that the work item from today still not present.

Can anyone advise what can be done?

Note: it seems it took 90 minutes to get the data refreshed. Can be this time make shorter?

Best Regards,

Judit

Accepted answers

Judit Gal

The answer I received is as follow:

How long can it take for new work items to appear in the dashboard?

You are correct in your understanding:

The jira_issue table (and a few other major Jira tables) in the Atlassian Data Lake is not updated in real time.

Updates to this table typically occur every 3 to 8 hours, depending on system load and your region. In some cases, it may be closer to 5–8 hours for changes to appear.

This means that a new work item created in Jira may not show up in your Analytics dashboard for several hours, regardless of your dashboard’s cache settings or manual refreshes.

Even if the dashboard says “Chart data updated a few seconds ago,” it only means the dashboard has fetched the latest data available in the Data Lake, not that the Data Lake itself has ingested the most recent Jira changes.

Why does manual refresh not bring in new data?
Manual refreshes and cache expiration only control how often the dashboard queries the Data Lake. If the Data Lake itself hasn’t ingested the new work item yet, the dashboard cannot display it, even if you refresh manually or see a recent “data updated” timestamp.

What this means for your test:
If you created a work item at 11:11 and it’s still not visible at 13:13, this is expected behavior for the jira_issue table. The delay is due to the Data Lake ingestion cycle, not your dashboard settings. In some cases, it may take up to 8 hours for new work items to appear.

All comments

Valerie Knapp_gp7rpj

Hi @Judit Gal , thanks for your post.

Have you already modifed the cache settings here - https://support.atlassian.com/analytics/docs/dashboard-settings/ ? or are you saying even with the cache set to 2 minutes, it still takes 90 minutes to refresh?

If that is the case, you need to open a support ticket to Atlassian and get them to look into this for you - https://support.atlassian.com/contact/

Best wishes

Judit Gal

Hi @Valerie Knapp , thank you for your response. I opened a ticket.

Just to confirm, yes the setting was set to 30 minutes as for the data considered to be updated and at the checking the cash for 2 minutes. I did further test today and I can confirm that the refresh is not happening - automatically or manually - for several hours.

Let's see how it goes...

Regards,

Judit

Judit Gal

The answer I received is as follow:

How long can it take for new work items to appear in the dashboard?

You are correct in your understanding:

The jira_issue table (and a few other major Jira tables) in the Atlassian Data Lake is not updated in real time.

Updates to this table typically occur every 3 to 8 hours, depending on system load and your region. In some cases, it may be closer to 5–8 hours for changes to appear.

This means that a new work item created in Jira may not show up in your Analytics dashboard for several hours, regardless of your dashboard’s cache settings or manual refreshes.