Mark the success path
A Jira administrator adds an authenticated RuleWatch heartbeat at the end of the rule's successful execution path.
RuleWatch for Jira
When a success signal goes quiet, take a closer look.
RuleWatch helps Jira administrators notice when a predictable recurring Automation rule has not sent its expected success-path heartbeat. It puts an investigation prompt where your team already works: Jira.
How it works
One heartbeat. One clear job.
Set the window
Choose the expected interval and a grace period. RuleWatch looks for the next heartbeat within that window.
Get one incident
After the first heartbeat, an overdue signal prompts one Jira incident when delivery succeeds. Later checks during that outage do not create duplicates.
See the return
When a heartbeat resumes, the monitor becomes healthy and RuleWatch adds one recovery comment to the existing incident when delivery succeeds.
Set up a destination you can check.
Choose a Jira project and compatible work type using guided selectors. Use the project default assignee or choose an assignable person. Read-only checks flag unsupported required fields and permission problems before you save. Send test incident checks delivery with a real labeled work item and comment, without changing monitoring state.
Connect Jira Automation with a one-time Bearer secret in a hidden Authorization header. Rotate the secret if exposed. Checks run about every five minutes after the expected interval plus grace period; a heartbeat records an observed signal, not proof of the underlying business result.
Set up RuleWatchAn honest signal
Know what was observed.
A missing heartbeat means RuleWatch did not observe completion of the monitored success path within the configured interval and grace period.
What it does not prove: the Jira Automation failed, was disabled, or had any particular root cause. Check the rule's audit log and final web request to understand what happened.