Auto refresh of issues when the status is changed by Listeners

[Srividhya]

I need to refresh the issue automatically ,when status of the issue has been changed automatically by the listeners.Currently , we need to refresh the issue to get the new status in the issue.

[Muhammad Ramzan(Atlassian Certified Master)]

Is there any update on this thread z

Plz.i am integrating jira with jenkin and updating status for many calls. User have to refresh the page to see the updates,  it looks weird from user experience 

[Nic Brough -Adaptavist-]

Er, how do you expect a client browser to know when information has been updated on a server?

Think about this carefully - Jira has a load of information that it shows to a user who asks "show me this page". If you want an "automatic" update, then somehow, you need the *Server* to tell all the *clients* that something is out of date and that there is new information. That is NOT how browsers work.

In fact, to make this work, you actually need to re-write the browser.

The best you can do is embed a "refresh after a while" instruction in the web page being served. This is generally bad practice though, as you impose a mostly pointless load on client and server just to check IF something has changed.

[Srividhya]

Actually , what we thought was like , we have a field , and in its description add a javascript function which reloads the page , but then we thought this would happen unnecesarily , even there is no change in the status. Anyways , thank you very much for your reply.

[Nic Brough -Adaptavist-]

Yes, javascript is a very good way to do it, you're spot on there. It is a sticky problem because of the basic question - how does the client know that data on the server has changed? Exactly as you say, the only way to do it is "unnecessarily" poll the server regularly. That feels wrong to me, but I can't think of a work-around.

[Jesse Glick]

Confluence already does this, so why could JIRA not do the same?

[Thomas Robertson]

Google docs allows multiple people to work on a document at a time and see changes keystroke by keystroke.  The fact that Jira requires me to reload the whole website every time I change something in a seperate tab has to be a solveable problem.

[Tom Wilson]

Please add this in.  We just migrated from Trello where this is standard practice and refreshing a page to see changes while working with a remote team is a huge step backwards from using Trello.  

[Kelly Clowers]

Agreed, would be nice to see it auto refresh or at least notify you it needs refreshed like confluence does.

[lee_conlin]

> Er, how do you expect a client browser to know when information has been updated on a server?

Websockets / SignalR ?

[Nic Brough -Adaptavist-]

Which you didn't have in 2012

[lee_conlin]

However, we're now in 2020 and do have it, and have had it for some time. 

Every other project management solution I've worked with over the last 5 years has had the ability to automatically update based on other users changes to enable fast and effective collaboration. The fact that this feature is still not part of Jira is ridiculous.

[lee_conlin]

Also worth pointing out that although web sockets weren't a thing in 2012, other options to achieve a similar feature were - long-polling, etc.

[Rudolph De Carvalho]

Guys its 2021, this shouldnt be an issue and we shouldnt have to refresh a page to see latest updates, so many other systems do this, I just moved from spiceworks that did it, having to rely on employees to refresh or remember to refresh to see the latest updates shouldnt happen

[travis_jones]

After using Trello for years and recently migrating to Jira, it feels like a step backwards. This feature is very much needed.