Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. Change integration
  • Introduction
  • On-call
    • Getting Started
      • Quick start
      • FAQ
      • Product Comparison
    • Incidents
      • What is an Incident
      • View Incidents
      • Handle Incidents
      • Escalations and Assignments
      • Custom Fields
      • Custom Actions
      • Alert Noise Reduction
      • Past Incidents
      • Outlier Incidents
    • Configure On-call
      • Channels
      • Integrate Alerts
      • Alert Noise Reduction
      • Escalation Rules
      • Label Enrichment
      • Schedules
      • Templates
      • Service Calendars
      • Preferences
      • Alert Routing
      • Silence and Inhibition
      • Filters
      • Notification Bots
      • Alert Pipeline
    • Advanced Features
      • Referencing Variables
      • Dynamic Assignment
      • Insights
    • Integrations
      • Alerts integration
        • Standard Alert Integration
        • Email Integration
        • Nightingale/FlashCat Integration
        • Prometheus Integration
        • Grafana Integration
        • Zabbix Integration
        • Uptime Kuma Integration
        • Alibaba Cloud ARMS Integration
        • Alibaba Cloud Monitor CM Event Integration
        • Alibaba Cloud Monitor CM Metrics Integration
        • Alibaba Cloud SLS Integration
        • AWS CloudWatch Integration
        • Azure Monitor Integration
        • Baidu Cloud BCM Integration
        • Huawei Cloud CES Integration
        • Influxdata Integration
        • Open Falcon Integration
        • PagerDuty Integration
        • Tencent BlueKing Integration
        • Tencent Cloud CLS Integration
        • Tencent Cloud Monitor CM Integration
        • Tencent Cloud EventBridge
        • OceanBase Integration
        • Graylog Integration
        • Skywalking Integration
        • Sentry Integration
        • Jiankongbao Integration
        • AWS EventBridge Integration
        • Dynatrace Integration
        • Huawei Cloud LTS Integration
        • GCP Integration
        • Splunk Alert Events Integration
        • AppDynamics Alert Integration
        • SolarWinds Alert Events Integration
        • Volcengine CM Alert Events Integration
        • Volcengine CM Event Center Integration
        • Volcengine TLS Integration
        • OpManager Integration
        • Meraki Integration
        • Keep Integration
        • ElastAlert2 Alert Integration
        • StateCloud Alert Events
        • Guance Alert Events
        • Zilliz Alert Events
        • Huawei Cloud APM Alerts
        • zstack integration
      • Change integration
        • Standard Change Event
        • Jira Issue Events
      • IM integration
        • Feishu (Lark) Integration Guide
        • Dingtalk Integration
        • WeCom Integration
        • Slack Integration
        • Microsoft Teams Integration
      • Single Sign-On
        • Authing Integration
        • Keycloak Guide
        • OpenLDAP Guide
      • Webhooks
        • Alert webhook
        • Incident webhook
        • Costom action
  • RUM
    • Getting Started
      • Introduction
      • Quick start
      • FAQ
    • Applications
      • Applications
      • SDK Integration
      • Advanced Configuration
      • Analysis Dashboard
    • Performance Monitoring
      • Overview
      • Metrics
      • Performance Analysis
      • Performance Optimize
    • Error Tracking
      • Overview
      • Error Reporting
      • Issues
      • Source Mapping
      • Error Grouping
      • Issue States
      • Issue Alerting
    • Others
      • Terminology
      • Data Collection
      • Data Security
  • Platform
    • Teams and Members
    • Permissions
    • Single Sign-On
  • Terms
    • Terms of Service
    • User Agreement/Privary Policy
    • SLA
    • Data Security
  1. Change integration

Jira Issue Events

Synchronize Jira Issue events to Flashduty via webhooks to collect change events.

Limitations#


In Jira#

You must have permission to modify Settings=>System=>Webhooks.
(For self-hosted deployments) Your Jira server must be able to access the domain api.flashcat.cloud.

Supported Versions#


This guide is compatible with both Jira Cloud and Self-hosted versions.

Setup Steps#


In Flashduty#

1.
Go to the Flashduty console, select Integration Center=>Change Events to enter the integration selection page.
2.
Select Jira integration:
Integration Name: Define a name for this integration.
3.
Click Save and copy the newly generated push URL for later use.
4.
Done.

In Jira#

1.
Log in to your Jira
2.
Go to Settings=>System=>Webhooks page, click the Create button
3.
Enter the callback URL as the push URL from your integration, and check Issue Created/Updated/Deleted event types
4.
Optionally, enter JQL to further narrow down the scope of events to sync (such as specific Projects)
5.
Click the Save button to submit the configuration
drawing
5.
Done

Status Mapping#


Flashduty extracts the status.name information from the webhook payload by default and converts the status according to the following mapping:
JiraFlashdutyStatus
plannedplannedCreated
to doplannedCreated
readyreadyAbout to Start
processingprocessingIn Progress
openprocessingIn Progress
reopenprocessingIn Progress
in progressprocessingIn Progress
canceledcanceledCanceled/Rolled Back
abortedcanceledCanceled/Rolled Back
donedoneCompleted
resolveddoneCompleted
closeddoneCompleted
Please contact Flashduty if you wish to modify this mapping.

添加官方技术支持微信

在这里,获得使用上的任何帮助,快速上手FlashDuty

微信扫码交流
上一页
Standard Change Event
下一页
Feishu (Lark) Integration Guide
Built with