LivePulse for Jira

"This issue changed" alerts for Jira and Jira Service Management. When someone else updates or comments on the issue you have open, you get an alert with a Refresh button, so you never edit or reply to a stale version. By PuzariCloud. Runs on Atlassian.

What it does

How it works

LivePulse listens for the change events that Jira sends to the issue view. As a safety net it also checks the issue's last-updated time while the issue is on screen (every 20 seconds by default, and once a minute after live events have been seen working). When the time moves, it reads the issue's history and latest comments once, using your own Jira permissions, to work out who changed what. Checks pause while the browser tab is in the background and run again as soon as you come back.

Settings (Jira admins)

Go to Jira settings → Apps → LivePulse settings. The settings apply to the whole site.

Limits

Moving from a Connect app or a workaround

If you used a Connect add-on, a browser extension or a "please reload before replying" rule to deal with stale issues (Atlassian request JSDCLOUD-433), nothing needs to be migrated. LivePulse keeps no data of its own: install it, optionally pick the settings, and every issue view is covered. Connect apps can no longer be updated, while LivePulse is built on Forge and runs entirely on Atlassian.

Support

Email support@puzaricloud.in. Privacy: privacy policy.