I added this comment to the issue in Jira Service Management Cloud, JSDCLOUD-433 but it looks like it really probably belongs here because we use Data Center

Is there a separate issue to address the 90253c67a11f  finding, specifically these:
Customer portal view 

1. When an agent comments, the page does not auto-refresh
2. When and agent transitions the issue, the page does not auto-refresh
3. When a field is edited, the page does not auto-refresh
4. When a form is added, either manually or via a rule, the form does not automatically appear

The lack of refreshing on the portal view is a big problem for us as we have a large number of request where agents or automation rules add Forms to the customer requests. We're dependent on the reporters checking their notifications. Which many are not very good at doing. 
 

This is a big issue for our customers as well

Unbelievable.

Not implemented now. The Ticket is open since 2014. Whats wrong with u atlassian? 

This is a must have. Please implement as soon as possible. Thanks.

Keen to get this resolved, annoying that I have to keep refreshing my pages to see if there are any updates.

@Willem So awesome! Somebody is offering Atlassian programming skills for free, because they don't maintain their product! LMAO!

Hello from 2023. Can I help implement this for free? I'm a coder.

This is a very basic function. I am dissatisfied that Atlassian is missing this basic part. Our agents press the F5 (refresh) button every 10 seconds. Is this the direction Atlassian wants?

+1

Atlassian, please implement this. It can't be that we need to talk about an event triggered auto refresh of an HTML page in 2021. As @dfranklin2 said ... this should be a core function.

Queues should definitely be able to refresh automatically based on any updates. This will make the helpdesk alot more productive especially for incoming or updating clients on changes.

Probably the best workaround for this is to create a Kanban board for your Service Desk with a quick filter that hides everything except issues assigned to currentUser() and unassigned.

Put in a post function on the transition from Open to In Progress that auto assigns to the current user, and everybody will only be able to see work available for them to work on.  If someone else "claims" an issue, it disappears from the board.

If you can get used to the side panel view for interacting with your issues, you need never open the ticket in full view mode (where you lose any awareness that someone else might be working on the same issue as you). 

Is there any news on an updated version of Issue Edit Notifications Plugin compatible with latest Jira ? It seems important and coming from a Zendesk environment it's a must for us

When can we have this functionality? This is really important for companies, such as mine, where many issues flow in and multiple people work on them simultaneously. 

+1 - I would have thought this sort of feature would be core functionality...

Please can we add this feature? Knowing when a ticket reply from customer or made by agent without refreshing the page would be very useful. Particularly for fractured teams who all work on Pull ticket assign or shared queues. 

+1 Please add this feature!

Since JIRA 7 the JIRA Quick Reload / Issue Edit Notifications Plugin works not in Service Desk context:
https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.quickreload/server/overview

This was a good workaround.

This is an awesome idea and one of the pain points in the ticket system we are using now. If this feature were in Jira we would definitely switch.

is this implemented? We are using JIRA service desk cloud and need the page to auto refresh very badly. Gmail, github all have this. The main purpose of service desk is to capture issue needs on a timely basis and act upon it. Without this feature, my team is missing out on the updates when they have the issue page open and someone else comments before they make a change.

+1 Please add this feature!

Please also vote and comment on JSD-404 and JSD-726

How are agents supposed to know a new ticket has arrived? no audible alert, no page reload. This seems like a basic required functionality, not a nice to have.

How is a team supposed to track SLA's when they are static? Keep in mind not everyone works exclusively on queues. Most of our staff have 4 monitors and don't have time to keep updating tabs - too much mental bandwidth goes toward remembering to do so.
Browser plugins to accomplish this are a mess - it requires us to install them on every staff's computer, properly configure it, ensure they don't mis/reconfigure it, etc. Plus it reloads the entire tab, which is more distracting (flickering window) and takes longer than "in-window" refreshing.
If resource load is a concern, what about in-page refreshing like has been added to the bottom of the Issue Navigator? This could be done every 5-15 minutes and still be way ahead of requiring a manual refresh.
Queues is a nice idea, but without auto-refresh (and a couple of other seemingly simple tweaks) it loses out to JIRA Agile workboards, the issue navigator and even dashboards.

+1

+1