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
- Watches every issue you open in the Jira issue view, in Jira and in Jira Service Management agent views.
- When another person changes a field or adds or edits a comment, Jira shows an alert such as "SUP-12 updated by Alice Ng: New comment · Status → Resolved", with Refresh and Dismiss.
- Refresh updates the issue view in place, without reloading the page.
- Your own changes never raise an alert. Changes by Automation for Jira and other apps are ignored unless your admin turns them on.
- The Live changes panel in the issue's details sidebar lists the last five changes by others since you opened the issue and shows whether the watcher is running. Check now checks the issue at once and tells you the result ("Checked — no new changes" or how many new changes it found).
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.
- Alert with a Refresh button (default): nothing changes on screen until the user clicks Refresh, so a half-typed comment is never lost.
- Refresh automatically when it is safe: refreshes straight away if the tab is in the background or the user has just come back to it. While the user is working it shows the alert only (no Refresh button), then refreshes by itself as soon as they switch away from the tab or come back to it.
- Alert on: field changes, comments, and (off by default) changes by automation rules and apps.
- Safety-net check: every 15, 20, 30 or 60 seconds, or live events only.
Limits
- Alerts appear only while an issue is open in the full issue view or the issue dialog. Boards, lists and the customer portal are not watched in this version.
- With the safety-net check, a change can take up to the check interval to appear (20 seconds by default). Live events usually arrive within a few seconds.
- Changes that Jira does not record in the issue history or comments (for example a worklog) appear as "updated by another user", and only when Jira's live event names someone else.
- The browser cannot see what you are typing in Jira, so "auto" mode refreshes only when the tab is hidden or has just been reopened.
- Settings are site-wide; per-project settings are planned.
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.