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

Reload issue page after rule triggered and comment created



we've created a rule using project automation which has:

  • a trigger on field
  • a condition on the field
  • two actions, including one that creates a comment on the issue

I expected the issue to be reloaded/refreshed in the browser so that the user can see the changes that were triggered, however, I can't seem to get that done. Please tell me how that works.

1 answer

1 accepted

0 votes
Answer accepted
Mykenna Cepek
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 29, 2020

I don't believe that Automation in Jira has any feature to force a refresh in the user's browser.

The Jira browser page will sometimes detect that something in the project has changed, and display a prompt to refresh the page. But in my experience, that is intermittent.

What I've found is that page refreshes in Jira are just something Jira users just need to get good at (especially when using Automation in the background).

I know this isn't the answer you were hoping for, but that's my experience. I've been using Jira for over 10 years, and Automation in Jira quite heavily for over a year.

Thank you for your reply, Mykenna. You are right, that is not the answer I wanted :) but I guess we need to get used to refreshing pages ourselves. Althought that is  really not what I would expect from a paid service like Jira Cloud.

Like # people like this

I totally agree! How is it that if a team-mate does something in their browser, I will see that in my browser within a few seconds, but if automation runs something on the server, that is not propagated out to the client browsers, not even to the browser that committed the action which fired the trigger? It's a bit lame.

Like # people like this

I suggest people vote for this issue: AUTO-171.

Like Johnny Hermann likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events