Skip to main content
Plan requirement: This feature requires the On-call Standard plan or above. Learn more
Create a webhook in Jira that subscribes to issue created, updated and deleted events to sync issues to Flashduty On-call. Each issue is one Flashduty change, and the change status follows the issue status (status.name). This fits teams that track change requests or releases as Jira issues. The integration works with Jira Cloud and Jira Data Center / Server.
This page brings Jira issues in as change events. To create a Jira issue automatically when a Flashduty incident occurs and keep the two in sync, use Jira Sync.

​
In Flashduty On-call

  1. In the Flashduty console, go to Integration Center → Change Events
  2. Select Jira and enter an integration name
  3. To assign changes to a specific channel, add rules under the integration’s Routing based on labels (for example project)
  4. Click Save and copy the generated Push URL

​
In Jira

1

Check permissions and network

  • Creating a webhook requires Jira administrator permission (site admin on Jira Cloud, Jira system administrator on Data Center / Server)
  • Jira Data Center / Server must be able to reach the push URL’s domain (api.flashcat.cloud)
2

Create the webhook

  1. Jira Cloud: go to Settings (gear icon) → System → WebHooks. Data Center / Server: go to Administration → System → WebHooks
  2. Click Create a WebHook and set URL to the full push URL of the Flashduty integration
  3. Under Events, select Issue created, updated and deleted
  4. Optionally limit the scope with JQL, for example project = OPS AND issuetype = Change to sync only change requests
  5. Leave Exclude body unchecked. Flashduty reads the request body
  6. Click Create
Flashduty authenticates the request with the integration_key in the push URL. The webhook secret is not verified, so leave it empty.
3

Verify

Create an issue that matches the JQL, or change the status of an existing one. The change appears in the Flashduty change list.

​
What a change is

Issue updated pushes are handled the same whatever the update type (issue_event_type_name): a transition, resolve, reopen, assignment or comment push updates the same change by the issue’s current status. The following pushes return success without creating a change: events other than issue created, updated and deleted, such as comment, worklog, sprint, version and project events.

​
Status mapping

Flashduty reads the issue’s status.name from the push, case-insensitively, and converts it as follows: If the status name is not in the table (for example a custom Waiting for Approval, or a localized status name), the push returns InvalidParameter and that push does not create or update a change. If your workflow uses other status names, contact us to configure a custom mapping for the integration. When an issue is deleted, Flashduty updates the change with the issue’s status at deletion time. The change is not set to Canceled automatically.

​
Change content

The title and description come from the first push of the change and are not updated afterwards. Status and labels follow later pushes; a push whose event time is earlier than the last recorded one (delayed or redelivered) does not overwrite them. Labels can be used for routing and for filtering in the change list:

​
FAQ

  1. Check that the issue matches the webhook’s JQL and that the webhook subscribes to the updated event
  2. Check that the new status name is in the status mapping table. Otherwise the push returns InvalidParameter, which shows in the Jira webhook’s delivery history
  3. Check that Exclude body is not selected on the webhook
  • issue status "<name>" is not mapped to a change status: the issue status is not in the mapping table. Contact us to configure a custom mapping
  • issue is empty / issue.key is empty / issue.fields is empty / issue.fields.status is empty: the body is incomplete. Make sure the push comes from a native Jira webhook with Exclude body unchecked
  • request payload is empty or a JSON decode error: the body is empty or not valid JSON
Standalone comment events (comment created and so on) do not create changes. When an issue is commented on, Jira also sends an issue updated push, which refreshes the change’s status and labels without creating a new change.