Refresh issue after any updates

[Petr AST]

Hi dear community! 

Recently, there has been a problem that the issue is not updated after making any changes by another project user. For example, the status was changed or a comment was written, but if the issue was opened on the browser page, then it will not be updated - you have to manually refresh the page.

This adds a lot of unnecessary actions, does everyone have such a problem?
Thanks! :)

Regards,
Petr

UPD: please vote for this issue https://jira.atlassian.com/browse/JSDCLOUD-433

[Dirk Ronsmans]

HI @Petr AST ,

That is indeed default behavior. Normally when another user saves or an automation changes the issue, you should see a popup that the issue was updated and that you should refresh.

It can however see Atlassian's point of view here too. If someone changes a field on your issue while you are typing a huge comment you don't want the screen to just auto refresh and you lose your information.

So yes, (unfortunately) everyone has that same issue :)

[Petr AST]

Hi @Dirk Ronsmans 
Thanks for your answer!

Their point of view is very strange. It contradicts itself. Now I checked for the sake of a test, an hour passed, the notification about the change in the data in the issue did not appear, although the status and comment and fields were changed. Okay, 5 seconds, okay a minute - but an hour, it's no good anyway.

The example with a comment also seems to me not entirely relevant, because all unfinished comments are saved when the page is refreshed (in cloud version).

It seems to me that they just broke the algorithm for updating the issue and notification. Can we create a collective request?

[Dirk Ronsmans]

Well yes maybe my example with the comment wasn't a 100% thought out :)

I do see the notification when you run an automation rule for example.

A collective request is always possible. You can go through support: http://support.atlassian.com/contact or you can go to https://jira.atlasssian.com/projects and raise a suggestion there :)

If you share it afterwards we can always vote on it

[Petr AST]

Hi there! 
@Dirk Ronsmans @nwr-fl 

Here is a link to an open request for this issue. Nothing has changed since 2014

https://jira.atlassian.com/browse/JSDCLOUD-433 

If you wish, you can influence this question)