Prerequisites
- This integration is compatible with Jira Cloud, as well as Jira Server and Jira Data Center versions 7.x and 8.x.
- Currently only supports one-way synchronization of incident information or status to Jira; information in Jira will not sync to Flashduty.
- For Jira Cloud, enter the API Token in the authorization configuration password field; for Jira Server or Data Center, use your Jira account login password.
Get API Token in Jira Cloud (Skip for Jira Server and Data Center)
- After logging into Jira Cloud, click the avatar in the top right corner and select Manage Account.
- On the Manage Account page, select the Security tab.
- On the Security page, click Create and manage API tokens.
- In the Create and manage API tokens dialog, enter the API token name and select an expiration time.
- Click Create to create the API token.
- After creation, copy the API token value and paste it into the API Token field in Flashduty authorization configuration.
Configure Integration in Flashduty On-call
1. Create and Authenticate Jira Integration
In Integration Center, select Webhook, choose Jira Sync integration, and fill in the following authentication information.
- Jira Platform Type: Select based on your version. For Data Center version, select Private (Server).
- Service Address: For Cloud version, enter your actual access address, e.g., https://your-domain.atlassian.net; for Server version, enter your service access address, e.g., https://your-jira-server-url.com.
- Username: Your Jira account name. For Cloud version, enter your email; for Server version, enter your Jira account name.
- API Token/Password: Your Jira account password. For Cloud version, enter the API Token; for Server version, enter your Jira account password.
- After filling in, click Next for further configuration.
2. Jira Integration Configuration
- Integration Name: Define a name for the current integration.
- Managing Team: Select the team that manages this integration; only team members can edit the integration configuration.
- Trigger Mode:
- Auto Trigger: Configure conditions; Flashduty On-call will automatically sync incidents matching the conditions to Jira.
- Manual Trigger: Manually trigger Jira sync from More Actions in incident details (the integration configuration name is the trigger name).
- Project ID: Select the project to sync to in Jira.
- Issue Type: Select the issue type to sync to in Jira.
- Channel: Select channels where this integration takes effect; only incidents in these channels can sync to Jira.
- Severity Mapping: Cannot be configured if the selected issue type doesn’t support the priority field. The Jira Priority (result field) is required for each mapping row; the integration cannot be saved if any row is missing it.
- Status Mapping: Maps the three Flashduty progresses Triggered, Processing and Closed to Jira statuses. The options are all statuses Jira provides for the selected Project ID + Issue Type.
- Leave all three empty to use the default mapping. As soon as you configure one of them, the other two become required and the integration cannot be saved without them (the error is Jira status is required).
- Changing the Issue Type clears the configured status mapping. Changing the Project ID clears the selected Issue Type, so you need to select the issue type again and re-check whether the status mapping still applies.
- When no mapping is configured, the Status Mapping field on the integration detail page shows Use default mapping.
- Custom Field Mapping: Optionally sync some or all incident labels, custom field content, and incident properties to Jira fields (only text-type fields supported). Both the Key (incident field) and the Result Field (Jira field) are required for each mapping row; the integration cannot be saved if any row is missing either.
- Apart from All labels, the Key dropdown options fall into three groups: Incident properties (Incident ID, Incident link), Labels (an individual label name), and Fields. Selecting Incident ID writes the incident ID; selecting Incident link writes the URL of the incident detail page in Flashduty.
3. About Updates
- For incidents that have already created Issues, if you update severity or status, Jira will auto-update, but Jira updates won’t sync to Flashduty.
- Comments sync to Jira, but Jira comment updates won’t sync to Flashduty.
- Updates to title, description, labels, and other fields in incidents won’t update in Jira.
4. Flashduty to Jira Mapping
Field Mapping
Status Mapping
When all three fields of Status Mapping in the integration configuration are left empty, the system syncs incident progress using the default mapping below:
The default mapping matches by name: the target names are
待办 / 处理中 / 完成 in a Chinese Jira and To Do / In Progress / Done in an English Jira. If the current status of the issue already carries the target name, no transition is needed; otherwise the system looks for a transition whose name equals the target name.
If your Jira workflow uses other status or transition names, the default mapping may find no matching transition. In that case, assign one Jira status to each progress in Status Mapping of the integration configuration. Once configured, status synchronization follows that mapping only; if one of the mapped Jira statuses has been deleted, the integration detail page shows Status not found (ID: xxx).
5. Notes
- Flashduty On-call syncs information according to default field mapping and your configured custom field mapping. If your Jira issue type has required fields without mapping configuration, Jira Issue creation will fail.
- Jira Issue details are accessed using the format Project KEY + number. If you modify the project KEY, you may not be able to access via the Issue URL saved in Flashduty—modify the project KEY with caution.