Jira Integration — Recommendations Become Tickets, Statuses Stay in Sync
What does the Jira integration do?
Recommendations become fully-formed Jira issues carrying the resource, monthly saving, remediation steps and a deep link. Sync runs in 2 directions: close in ZopNight and the ticket resolves with a comment, move the ticket and the recommendation follows. A deterministic fingerprint label prevents duplicate filing across refreshes.
Coverage by category
Cost work only happens when it lands in the backlog. ZopNight’s Jira integration turns any recommendation into a fully-formed Jira issue, either on demand or automatically through policy. The issue carries the resource, location, monthly savings, remediation steps and a deep link. Statuses then stay in sync in both directions: close it in ZopNight and the ticket resolves with an explanatory comment; move the ticket in Jira and the recommendation follows.
Fingerprint labels, adopted issues, and the webhook
Connect with your Jira Cloud site URL, an Atlassian account email and an API token (classic and scoped tokens both work; ZopNight auto-detects). Tickets are created with a deterministic fingerprint label so duplicates are never filed, even across recommendation refreshes; if a matching open issue already exists, ZopNight adopts it. For inbound sync, ZopNight registers a signed webhook on your Jira site automatically (requires a Jira admin; without it, outbound-only mode works and ZopNight tells you). Automatic ticketing is policy-driven: route every recommendation, or only specific categories, to a project with a default issue type and assignee.
Site URL, account email, token, then pick a project
- Create an Atlassian API token.
- Settings > Integrations > Jira: enter site URL (your-org.atlassian.net), account email and token, then Verify connection.
- Pick a default project and issue type.
- Choose an automatic-ticketing mode: set up later, all recommendations, or specific recommendations (opens the policy editor).
- Confirm two-way sync is active (requires the connecting account to be a Jira admin).
Ticketing, sync, and duplicate prevention
Manual one-click ticket creation from any recommendation. Policy-based auto-ticketing with project/issue-type/assignee routing. Two-way status sync with human-readable comments. Assignee sync in both directions. Duplicate prevention via fingerprint labels. Notification event when a ticket is opened.
Limits worth knowing before you connect
Jira Cloud only (*.atlassian.net) — Jira Data Center and custom domains are not supported. Webhook registration requires a Jira admin account; scoped tokens cannot self-register the webhook.
Jira integration: common questions
Will a recommendation refresh file duplicate tickets?
No. Each issue is created with a deterministic fingerprint label, and if a matching open issue already exists ZopNight adopts it rather than creating a second one.
Do I have to be a Jira admin?
For two-way sync, yes: registering the signed inbound webhook on your Jira site needs a Jira admin account, and a scoped token cannot self-register it. Without admin, outbound-only mode works and ZopNight tells you that is what you have.
Does Jira Data Center work?
No. Jira Cloud only, on an atlassian.net site. Custom domains are not supported either.
No active rule family targets Jira Integration — Recommendations Become Tickets, Statuses Stay in Sync today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.