Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Auto refresh of issues when the status is changed by Listeners

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.

2 answers

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 

2 votes

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.

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.

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.

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

Like # people like this

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.

Like # people like this

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.  

Like # people like this

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

Like # people like this

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

Websockets / SignalR ?

Which you didn't have in 2012

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.

Like Kelly Clowers likes this

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.

Like Kelly Clowers likes this

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

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you