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

Why are my dashboards not updated live?

Patrick Roos_j4vwk9

On my dashboard, I show specific issues based on a filter.

If I change the status of an issue or I assign the issue to another person, the dashboard isn't updated for awhile. It needs 1 - 2 minutes until it's updated. Refreshing the browser doesn't help.

What can I do that after a refresh the issues are updated?

Thanks for your help.

Regards, Patrick

Accepted answers

Jack Brickey

Short of refreshing the browser nothing. The issue certainly should update with a screen update at least at the same rate that it would in the detail view.
I suggest checking how quick the issue updates in detailed view and maybe Kanban detailed view and compare to dashboard.
note, I’m not a fan of the 15m refresh on dashboards as it creates unnecessary (?) demand on the system performance.

All comments

KAGITHALA BABU ANVESH_z1zl10

Hi @Patrick Roos ,

By Default Jira Gadget refresh rate we have to set manually.

Minimal Interval time for refresh the Gadget on Dashboard is 15 minutes.

When evert you refreshed the browser, data should be refreshed. if you not getting the latest data means. There may be 2 problems.

1. Try to clear cache from browser.

2. Re-index entire Jira once. it will help to display the latest data without connecting DB.

3.Clear JAVA Virtual Memory, sometime if Memory is completely occupied, Data refresh may be delayed.

Thanks,

Anvesh

Patrick Roos_j4vwk9

Hi @KAGITHALA BABU ANVESH

Thank you for your answer and thanks for your help!

15 minutes refresh option

I have already seen this refresh option. For me, the problem is that the issues in the dashboard are not updated even after a refresh.

Step 1 - 3

The deployment type is 'Cloud' so I don't think I need to worry about the index or JVM options...:-)

Regards, Patrick

Jack Brickey

Patrick Roos_j4vwk9

Hi @Jack Brickey

Thanks for your answer!

> The issue certainly should update with a screen update at least at the same rate
> that it would in the detail view.

Nope, it doesn't update in the screen at the same rate that it would in the details --> this is exactly the problem :-)

>I suggest checking how quick the issue updates in detailed view and maybe Kanban >detailed view and compare to dashboard.

On the Kanban board the issue updates immediately and in the detail view, it takes 1 - 2 minutes...

> note, I’m not a fan of the 15m refresh on dashboards as it creates unnecessary (?) > demand on the system performance.

It's in the Atlassian cloud :-)

Jack Brickey

I just ran a quick test and had mixed results interestingly enough. I took one issue that was showing in a filtered list and in another screen changed the status. I went back to the dashboard and reloaded several times. It seemed to take ~10s before it picked up the change. I then went to do a recording so I could share w/ Atlassian Support. However, this time the change took w/ the first reload. Tried again and again one reload did the trick. I don't know what the refresh algorithm is TBH. You might want to work directly with Atlassian Support since they are the only ones that can log in and observe. If you can reproduce at will you might even do a screen recording and attach to your ticket.

if you do open a ticket keep us posted.

Tereza Červinková

Did you open the ticket? We have the same issue do wonder whether to write separately or they are already solving the problem.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud