Jira & Automation Rules¶
Create reviewer-approved Jira issues from comparison reports, and route webhook notifications conditionally — beyond the flat "every webhook gets every subscribed event" model described in API Access.
Requires a Business (or Enterprise) plan — same gate as API keys and webhooks.
Manage both from Workspace settings → Jira integration and Workspace settings → Automation.
Jira integration¶
Jira issues are reviewer-created, not automatic. A project mapping makes Jira available in that project's comparison viewer. Open a comparison, choose Create Jira issue, and confirm its summary and optional description. VisualRunner includes the report link, change signals, and the available baseline, candidate, and annotated-difference screenshots. It records the issue on the comparison so repeated clicks cannot create duplicates, and refreshes the Jira workflow status when the report is opened.
Resolving an issue in Jira does not dismiss its VisualRunner comparison. If attachment upload fails after the issue is created, the issue remains valid and the report shows an attachment warning.
- Open Jira integration and click Connect Jira. You'll be sent to Atlassian to authorize access to a Jira Cloud site — VisualRunner never sees your Atlassian password.
- Once connected, create a project mapping: pick a VisualRunner project, the Jira project key
it should create issues in (e.g.
ENG), and the issue type (e.g.Bug). - Click Send test on a mapping to confirm it actually creates an issue before relying on it.
A mapping can create one Jira issue per comparison. If the Jira connection expires or is revoked on Atlassian's side, creation fails until you reconnect — check Jira integration for a "reconnect" prompt if issues stop appearing.
Disconnecting removes the connection immediately; existing project mappings stay configured but stop being able to create issues until you reconnect.
Automation rules¶
Automation Rules route matching monitor events to webhooks. They no longer create Jira issues: creating external work requires a reviewer to confirm it from the comparison viewer.
An automation rule fires one or more webhook actions when its conditions match — additive routing on top of your existing webhook subscriptions and email preferences, which keep working unchanged whether or not any rule exists.
- Open Automation and click a condition for each dimension you want to filter on:
- When: which event kind(s) — visual/content change, run failed, run failing repeatedly.
- Environment: any, production only, or non-production only.
- Projects: leave every checkbox unchecked to match every project, or check specific ones.
- Pick one or more existing webhooks as actions.
- Save. The rule evaluates on every qualifying notification going forward — it doesn't apply retroactively to past events.
If more than one enabled rule matches the same event, every matching rule's actions fire — not just the first match. This is deliberate (a "business tier escalation" rule and a "production environment" rule might both want to fire independently), but worth knowing if you expect first-match-wins behavior.
Rules don't currently support monitor tags or tiers as a condition — only event kind, project, and environment. If a referenced webhook or Jira mapping is later deleted, the rule stops firing that action (the other actions in the same rule still fire).