Does jira automation rule need to refresh page to see the change?

[Kristy]

I create a simple automation rule, that is when field A=abc, then field B=xyz. It runs successfully, however I can only see field B change after I refresh the issue/page. Does it just work as it?

[Enric Font]

Dear @Kristy 

Yes, this can happen in Jira Cloud, and in many cases it is expected behavior.

When an automation rule updates an issue, the update is performed server-side. The issue view in your browser does not always receive a real-time notification for every field change, so some fields may not refresh until the page is reloaded.

Hope this helps

[Tinker Fadoua]

Hi @Kristy 

Can you please share a screenshot with your automation? Please hide any confidential info.

Best,

Fadoua

[James Gamble]

Hola Kristy,

@Enric Font is right. The automation is updating the work item on the server, but Jira Data Center doesn’t automatically refresh an issue page when another process changes it. If the automation audit log shows the rule completed successfully and field B has the correct value after a browser refresh, the rule itself is working.

This isn’t something the Re-fetch work item action would fix. That action refreshes only the data available in the automation rule, so later rule steps use the latest values. It doesn’t refresh the page open in the user’s browser.

Atlassian has an open suggestion for Jira Data Center to automatically refresh an issue when it changes.

So yes, with the current behavior, the user may need to refresh the page to see field B change. If the field still doesn’t update after refreshing, then I’d check the rule’s audit log and field context, but a display delay by itself isn’t evidence that the automation failed.

Thanks,

James