New
Jira Integration: Precise Field Mapping and Safer Two-Way Sync
The updated All Quiet Jira integration offers precise field mapping, two-way sync without loops, and better priority controls for incidents. These changes improve automation reliability and reduce manual configuration for teams.
Published: Monday, 31 August 2026
The updated All Quiet Jira integration offers precise field mapping, two-way sync without loops, and better priority controls for incidents. These changes improve automation reliability and reduce manual configuration for teams.
New Data Synchronization Settings
- Jira Priority for Incidents Created in Jira: Map All Quiet severity directly to Jira priority for critical, warning, or minor incidents. When severity changes, the system updates the linked Jira issue automatically.
- Default Values for Jira Custom Fields: All Quiet loads required custom fields from Jira (text, numbers, dates, labels, select lists). Set default values so automatic issue creation succeeds without missing mandatory fields.
- Sync Jira Fields as Incident Attributes: Select specific Jira fields for All Quiet to store as attributes on linked incidents. This provides teams with vital context directly inside All Quiet.
- Severity Mapping from Jira: Link Jira priorities to All Quiet severity.
Stability and Bug Fixes
- Two-Way Sync Safety: If a Jira webhook changes incident status or severity, All Quiet does not push that update back to Jira. This prevents endless loops between different integration rules.
- Clearer Error Messages: When Jira rejects an issue, outbound history logs display the specific field error rather than a vague HTTP failure.
- Optional Status Sync: Set status updates for resolved or reopened incidents to "(Don't sync)". All Quiet leaves the Jira status unchanged in these cases.
Incident Creation Filters
| Setting | New Behavior |
|---|---|
| Issue Statuses for Open Incidents | Matching issues create open incidents. Any status matches if left blank. |
| Issue Statuses for Resolved Incidents | Matching issues create resolved incidents. New incidents default to open if left blank. |
| Filter Labels to Create Incidents | Now features a searchable list of all labels used in Jira. |
Expanded Incident Attributes
Linked incidents now receive standard attributes for complete traceability:
- Jira Issue Key: The direct ticket identifier (PROJ-123).
- Jira Priority: The exact Jira priority name.
- Jira Project: The project name or key.
- Jira Description: Incidents created from Jira use this field. Subsequent Jira description updates modify only this attribute. This protects the original All Quiet description. Multiple Jira labels now save as a single comma-separated Label attribute.
Learn more in the Jira setup guide.
Updated August 31, 2026