flashduty-knowledge-base 1.2.4-beta.5 → 1.2.5

package/dist/en.d.ts

@@ -53,5 +53,6 @@ declare const docs: {
     CustomAction: string;
     Templates: string;
     HuaweiyunAPM: string;
+    JiraSync: string;
 };
 export default docs;

package/dist/esm/en.js

@@ -4051,7 +4051,7 @@ Choose this method when you need to route alerts to different channels based on
 |Notice|Info|Info|
 
 </div>
-`,N=`---
+`,P=`---
 title: "Volcengine Log Service (TLS) Alert Events"
 description: "Sync Volcengine Log Service (TLS) alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -4188,7 +4188,7 @@ Choose this method when you need to route alerts to different channels based on
 </div>
 
 </div>
-`,P=`---
+`,N=`---
 title: "OpManager Alert Events"
 description: "Sync OpManager alert events to Flashduty via webhook for automated alert noise reduction"
 date: "2024-07-05T10:00:00+08:00"
@@ -5246,7 +5246,7 @@ Integrate WeCom third-party application to receive and respond to alerts within
 7. **Incident notification fails with \`WeCom License Not Activated\`?**
 
    - Contact Flashduty customer service or dedicated support for license purchase and activation
-`,V=`---
+`,z=`---
 title: "Slack Integration"
 description: "Integrate with Slack to receive and respond to alerts within Slack"
 date: "2024-05-11T10:00:00+08:00"
@@ -5300,7 +5300,7 @@ Integrate with Slack to receive and respond to alerts within Slack.
 
 8. **Slack App shows Other questions error**
    - Try again, as this might be an unrecorded issue
-   - If the error persists, contact customer support`,z=`---
+   - If the error persists, contact customer support`,V=`---
 title: "Microsoft Teams Integration"
 description: "Integrate Microsoft Teams as a third-party application to receive and respond to alerts within Microsoft Teams"
 date: "2024-05-11T10:00:00+08:00"
@@ -5395,7 +5395,7 @@ Please check in Integration Center => Instant Messaging => Microsoft Teams under
 Currently not supported
 </details>
 
-`,K=`Configure alert webhooks to receive HTTP callbacks at your specified URL when alerts have specific actions (such as triggering or closing). The callback content includes the latest key information about the alert, allowing integration with your custom tools.
+`,J=`Configure alert webhooks to receive HTTP callbacks at your specified URL when alerts have specific actions (such as triggering or closing). The callback content includes the latest key information about the alert, allowing integration with your custom tools.
 
 <span id="EventTypes"></span>
 
@@ -5563,7 +5563,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 4. **Trusted IP whitelist for push sources?**
    - {ip_whitelist}
    - May be updated in the future, please check periodically
-`,Z=`Configure incident webhooks to receive HTTP callbacks at your specified URL when incidents have specific actions (such as triggering or closing). The callback content includes the latest key information about the incident, allowing integration with your custom tools.
+`,K=`Configure incident webhooks to receive HTTP callbacks at your specified URL when incidents have specific actions (such as triggering or closing). The callback content includes the latest key information about the incident, allowing integration with your custom tools.
 
 <span id="EventTypes"></span>
 
@@ -5586,6 +5586,7 @@ The following event types are currently supported, with more potentially being a
 |    i_rslv    | Close incident (automatically or manually) |
 |   i_reopen   | Reopen incident |
 |   i_merge    | Manually merge incidents |
+|   i_comm     | Add comment |
 |  i_r_title   | Update incident title |
 |   i_r_desc   | Update incident description |
 |  i_r_impact  | Update incident impact |
@@ -5769,7 +5770,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **Trusted IP whitelist for push sources?**
    - {ip_whitelist}
-   - May be updated in the future, please check periodically`,J=`Custom incident actions allow you to quickly invoke external interfaces during incident troubleshooting for incident self-healing, information enrichment, and other custom operations.
+   - May be updated in the future, please check periodically`,Z=`Custom incident actions allow you to quickly invoke external interfaces during incident troubleshooting for incident self-healing, information enrichment, and other custom operations.
 
 ## I. Creating Actions
 
@@ -6017,6 +6018,88 @@ When an incident occurs and is confirmed to be caused by a change, directly trig
 ### Update Status Page
 
 When an incident is confirmed to affect online services, trigger external status page updates to prompt`,Q=`---
+title: "Jira Sync"
+description: "Sync incidents with Jira issues through Jira Sync Webhook."
+date: "2024-05-11T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/jira-sync"
+---
+
+Through Jira Sync Webhook, you can associate and synchronize Flashduty incidents with Jira Issues, enabling integration between Flashduty and Jira.
+
+## Prerequisites
+- This integration is compatible with Jira Cloud, as well as versions 7.x and 8.x of Jira Server and Jira Data Center.
+- Currently, only one-way synchronization of incident information and status to Jira is supported. Information in Jira will not sync back to Flashduty.
+- For Jira Cloud, use an API Token in the password field during authorization configuration; for Jira Server or Data Center, use your Jira account password.
+
+## Getting API Token in Jira Cloud （Jira Server and Data Center please skip）
+
+- After logging into Jira Cloud, click your profile picture 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 an API token name and select an expiration time.
+- Click **Create** to generate the API token.
+- Copy the API token value and paste it into the API token field in Flashduty's authorization configuration.
+
+## Configuring Integration in Flashduty
+
+### 1. Create and Authenticate Jira Integration
+<div class="hide">
+
+In the Integration Center, select **Webhook**, choose **Jira Sync** integration, and fill in the following authentication information.
+
+</div>
+
+- **Jira Platform Type**: Choose based on your version. For Data Center version, select Self-hosted (Server).
+- **Service URL**: For Cloud version, enter your actual access URL, e.g., https://your-domain.atlassian.net. For Server version, enter your service access URL, 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 username.
+- **API Token/Password**: Your Jira account credentials. For Cloud version, enter API Token; for Server version, enter your Jira account password.
+- After completion, click **Next** to proceed with configuration.
+
+**About Permissions**: Ensure your Jira account has permissions to access relevant projects, issue types, and create issues. Using an administrator account is recommended.
+
+### 2. Jira Integration Configuration
+
+- **Integration Name**: Define a name for this integration.
+- **Trigger Mode**:
+    - Automatic: Configure conditions for Flashduty to automatically sync qualifying incidents to Jira.
+    - Manual: Manually trigger Jira sync from the incident details page's more actions menu (integration name serves as trigger name).
+- **Project ID**: Select the target Jira project for synchronization.
+- **Issue Type**: Select the target Jira issue type.
+- **Channel**: Select the channel where this integration will be active. Only incidents within this channel can sync to Jira.
+- **Severity Mapping**: If the selected issue type doesn't support priority fields, this mapping cannot be configured.
+- **Custom Field Mapping**: Choose to sync certain or all incident labels and custom field content to Jira fields (text type fields only).
+
+### 3. About Updates
+
+- For incidents with existing Jira issues, updates to severity or status will automatically update in Jira, but Jira updates won't sync back to Flashduty.
+- Comments sync to Jira, but Jira comments won't sync back to Flashduty.
+- Updates to incident title, description, labels, or other fields won't update in Jira.
+
+### 4. Flashduty to Jira Mapping
+
+#### Field Mapping
+
+| Jira | Flashduty |
+| ---------- | -------- |
+| Summary | Title |
+| Description | Description |
+| Priority | Severity |
+| Reporter | Integration configured user |
+| Comments | Comments |
+
+#### Status Mapping
+
+| Jira | Flashduty |
+| ---------- | -------- |
+| Todo | Pending |
+| In Progress | In Progress |
+| Done | Resolved |
+
+### 5. Important Notes
+
+- Flashduty syncs information according to default field mappings and your custom field configurations. If your Jira issue type has required fields without mapping relationships, Jira issue creation may fail.
+- Jira issue details are accessed using project KEY + number format. If you modify the project KEY, saved issue URLs in Flashduty may become inaccessible, so please modify project KEYs with caution.
+`,X=`---
 title: "Configure Notification Templates"
 description: "Customize notification content through template configuration"
 date: "2024-05-10T10:00:00+08:00"
@@ -6640,4 +6723,4 @@ If custom content is not set, the system default template will be used for notif
 As shown below:
 <img src="https://download.flashcat.cloud/flashduty/doc/en/fd/template-mail-1.png" width="800">
 
-`,X={CustomAlert:n,Email:t,N9e:a,Prometheus:i,Grafana:o,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:h,BaiDuBCM:u,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:L,Dynatrace:_,HuaweiyunLTS:F,GoogleCM:x,Zilliz:Y,Splunk:R,AppDynamics:T,SolarWinds:U,VolcEngineMetric:E,VolcEngineEvent:D,VolcEngineTLS:N,OpManager:P,Meraki:M,StateCloud:W,Guance:G,CustomChange:O,Jira:j,Lark:$,Dingtalk:H,Wecom:B,Slack:V,MicrosoftTeams:z,AlertWebhook:K,IncidentWebhook:Z,CustomAction:J,Templates:Q,HuaweiyunAPM:q};module.exports=X;
+`,ee={CustomAlert:n,Email:t,N9e:a,Prometheus:i,Grafana:o,Zabbix:s,UptimeKuma:r,AliyunARMS:l,AliyunCmEvent:d,AliyunCm:c,AliyunSLS:e,AWSCW:e,AzureMonitor:h,BaiDuBCM:u,HuaWeiCES:g,InfluxDB:p,OpenFalcon:m,PagerDuty:f,TencentBK:y,TencentCLS:v,TencentCm:b,TencentEb:w,OceanBase:C,Graylog:k,Skywalking:I,Sentry:S,Jiankongbao:A,AWSEventBridge:L,Dynatrace:_,HuaweiyunLTS:F,GoogleCM:x,Zilliz:Y,Splunk:R,AppDynamics:T,SolarWinds:U,VolcEngineMetric:E,VolcEngineEvent:D,VolcEngineTLS:P,OpManager:N,Meraki:M,StateCloud:W,Guance:G,CustomChange:O,Jira:j,Lark:$,Dingtalk:H,Wecom:B,Slack:z,MicrosoftTeams:V,AlertWebhook:J,IncidentWebhook:K,CustomAction:Z,Templates:X,HuaweiyunAPM:q,JiraSync:Q};module.exports=ee;

package/dist/esm/zh.js

@@ -3346,7 +3346,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/jiankongbao-integration-guide"
 |2|Info|提醒|
 
 </div>
-`,S=`---
+`,C=`---
 title: "AWS EventBridge 告警事件"
 description: "通过 webhook 的方式同步 AWS EventBridge 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-08-20T10:00:00+08:00"
@@ -3451,7 +3451,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/aws-eventbridge-integration-guide
 
 </div>
 
-`,C=`---
+`,S=`---
 title: "Dynatrace 告警事件"
 description: "通过 webhook 的方式同步 Dynatrace 告警事件到 Flashduty，实现告警事件自动化降噪处理。"
 date: "2024-08-20T10:00:00+08:00"
@@ -3565,7 +3565,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dynatrace-integration-guide"
 |CUSTOM_ALERT|Info|提醒|
 
 </div>
-`,L=`---
+`,I=`---
 title: "华为云日志服务 LTS 告警事件"
 description: "通过 webhook 的方式同步华为云日志服务 LTS 告警事件到 Flashduty，实现告警事件自动化降噪处理。"
 date: "2024-08-20T10:00:00+08:00"
@@ -3681,7 +3681,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/huaweilts-integration-guide"
 |Info|Info|提醒|
 
 </div>
-`,I=`---
+`,L=`---
 title: "GoogleCloudMonitoring 告警事件"
 description: "通过 webhook 的方式同步 GoogleCloudMonitoring 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4740,7 +4740,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/statecloud-integration-guide"
 
 
 </div>
-`,U=`---
+`,j=`---
 title: "观测云告警事件"
 description: "通过 webhook 的方式同步观测云告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -4828,7 +4828,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/guance-integration-guide"
 | 数据断档     | Info     | 提醒 |
 
 </div>
-`,j=`---
+`,U=`---
 title: "zilliz 告警事件"
 description: "通过 webhook 的方式同步 zilliz 告警事件到 Flashduty，实现告警事件自动化降噪处理"
 date: "2024-07-05T10:00:00+08:00"
@@ -5252,14 +5252,34 @@ sidebarDepth: 3
     - 确保账户已经完成关联，前往 飞书 > 工作台 > 搜索应用名称 > 打开应用，完成一次登录并关联（飞书< - >Flashduty）账号。如果已经登录过，尝试点击右上角菜单，切换账户，重新登录来绑定账号
     - 确保已购买足够的 license，已使用 license 情况，可以在控制台 > 费用中心查看
 
-2. **分派策略飞书群聊列表为空**？
+3. **分派策略飞书群聊列表为空**？
 
     - 前往 飞书，选择群聊会话，添加已创建的Flashduty机器人，如下图所示：
     - 回到分派策略配置页面，刷新后重新选择群聊列表
 
 <img alt="drawing" width="800" src="https://download.flashcat.cloud/feishu-self-app-invite-to-chat.jpeg" />
 <img src="https://download.flashcat.cloud/feishu-self-app-notify-rule.png" alt="drawing" width="800"/>
-`,G=`---
+
+4. **飞书自建应用 API 限制：** [飞书文档说明](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/platform-updates-/custom-app-api-call-limit)
+
+    **调用量限制：**
+
+    |     飞书版本     | 调用总量/月 | 刷新时间  |                       
+    | :----------: | :--: | :----: |
+    |基础免费版|10,000 次|每个自然月的 1 号|
+    |其他版本|不限制|-|        
+
+    **频控限制：**
+
+    |    场景     | 限制 |                   
+    | :----------: | :--: | 
+    |所有接口|每个应用最高频率 50 次/秒|
+    |发消息接口|每个应用最高频率 1000 次/分钟|
+    |群机器人 Webhook|最高频率 100 次/分钟|
+    |给同一个用户或同一个群发消息|最高频率 5 次/秒|
+
+    **注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
+`,J=`---
 title: "钉钉集成"
 description: "通过集成钉钉自建应用，实现在钉钉端内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5410,7 +5430,16 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-integration-guide"
 
 <img src="https://download.flashcat.cloud/dingtalk-self-app-notify-rule.png" alt="drawing" width="800"/>
 
-`,V=`---
+4. **钉钉自建应用 API 调用量：** [钉钉文档说明](https://open.dingtalk.com/document/orgapp/descriptions-about-adjusting-limit-and-frequency-of-api-calls?spm=ding_open_doc.document.0.0.6f6b21d9WtkxJI)
+
+|     钉钉版本     | 调用总量/月 | QPS| 刷新时间  |                       
+| :----------: | :--: | :----: | :----:|
+|标准版|10,000 次|20|每月1日|
+|专业版|50万次|40|     每月1日          |
+|专属版|550万次|60|     每月1日          |
+
+**注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
+`,G=`---
 title: "企业微信集成"
 description: "通过集成企业微信第三方应用，实现在企业微信端内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5490,7 +5519,7 @@ url: "https://docs.flashcat.cloud/zh/flashduty/wecom-integration-guide"
 7. **故障通知失败，提示\`未开通企微许可\`？**
 
    - 联系 Flashduty 客服或专属支持，为您购买开通
-`,Z=`---
+`,V=`---
 title: "Slack 集成"
 description: "通过集成Slack第三方应用，实现在Slack内接收和响应告警的能力"
 date: "2024-05-11T10:00:00+08:00"
@@ -5639,7 +5668,7 @@ Microsoft Teams 集成现处于 Beta 阶段，在关联前您需要先完成以
 暂不支持
 </details>
 
-`,J=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
+`,Z=`配置告警 Webhook，当告警发生特定操作（如触发、关闭）时，系统通过 HTTP 回调您配置的地址。回调内容将包含告警最新关键信息，您可以与自研工具进行集成。
 
 <span id="EventTypes"></span>
 
@@ -5830,6 +5859,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 |    i_rslv    | 关闭故障（自动或手动关闭） |
 |   i_reopen   | 重新打开故障     |
 |   i_merge    | 手动合并故障     |
+|   i_comm     | 添加评论     |
 |  i_r_title   | 更新故障标题     |
 |   i_r_desc   | 更新故障描述     |
 |  i_r_impact  | 更新故障影响     |
@@ -6014,7 +6044,7 @@ curl -X POST 'https://example.com/incident/webhook?a=a' \\
 
 4. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,Q=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
+   - 未来可能会更新，请定期查验`,Y=`配置故障 自定义操作，允许您在故障排查期间，快速调用外部接口，实现故障自愈、信息丰富等任何自定义操作。
 
 ## 一、创建操作
 
@@ -6273,7 +6303,92 @@ curl -X POST 'https://example.com/incident/action?a=a' \\
 
 2. **推送来源可信 IP 白名单？**
    - {ip_whitelist}
-   - 未来可能会更新，请定期查验`,Y=`---
+   - 未来可能会更新，请定期查验`,Q=`---
+title: "Jira 同步"
+description: "通过 Jira 同步 Webhook，实现故障与 Jira Issue 的关联。"
+date: "2024-05-11T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/jira-sync"
+---
+
+通过 Jira 同步 Webhook，将 Flashduty 的故障与 Jira Issue 进行关联同步，实现 Flashduty 与 Jira 的联动。
+
+## 前提说明
+- 该集成兼容 Jira Cloud 以及 Jira Server 和 Jira Data Center 的 7.x 和 8.x 版本。
+- 目前仅支持将故障相关信息或状态单向同步到 Jira 中，Jira 中的信息不会同步到 Flashduty 中。
+- 对于 Jira Cloud，请在授权配置的密码处填写 API Token；而对于Jira Server 或 Data Center，则使用您的 Jira 账户登录密码即可。
+
+## 在 Jira Cloud 中获取 API Token （Jira Server 和 Data Center 请跳过）
+
+- 登录 Jira Cloud 后，点击右上角头像，选择 **管理账户**。
+- 在 **管理账户** 页面中，选择 **安全性** 选项卡。
+- 在 **安全性** 页面中，点击 **创建并管理 API 令牌** 按钮。
+- 在 **创建并管理 API 令牌** 弹窗中，填写 API token 名称，并选择过期时间。
+- 点击 **创建** 按钮，创建 API token。
+- 创建完成后，复制 API token 值，并粘贴到 Flashduty 授权配置中的 API 令牌处。
+
+## 在 Flashduty 中配置集成
+
+### 1. 创建并认证 Jira 集成
+<div class="hide">
+
+在集成中心，选择 **Webhook** ，选择 **Jira 同步** 集成，并填写以下认证信息。
+
+</div>
+
+- **Jira 平台类型**：根据您使用的版本进行选择，如果是 Data Center 版本的请选择私有化（Server） 即可。
+- **服务地址**：Cloud 版本请填写您的实际访问地址，例如： https://your-domain.atlassian.net，Server 版本请填写您的服务访问地址，例如： https://your-jira-server-url.com。
+- **用户名**：您的 Jira 账户名，Cloud 版本请填写您的邮箱，Server 版本请填写您的 Jira 账户名。
+- **API令牌/密码**：您的 Jira 账户密码，Cloud 版本请填写 API Token，Server 版本请填写您的 Jira 账户密码。
+- 填写完成后，点击 **下一步** 按钮，进行相关配置。
+
+**关于权限**：请确保您的 Jira 账户拥有获取相关项目、事务类型以及创建 Issue 等权限，建议使用管理员账户。
+
+### 2. Jira 集成配置
+
+- **集成名称**：为当前集成定义一个名称。
+- **触发模式**：
+    - 自动触发：需要配置相应的条件，Flashduty 会自动将符合条件的故障同步到 Jira 中。
+    - 手动触发：需要在故障详情页的更多操作中手动触发 Jira 同步（该集成配置的名称为触发器名称）。
+- **项目 ID**：选择需要同步至 Jira 的项目。
+- **事务类型**：选择需要同步至 Jira 的事务类型。
+- **协作空间**：选择该集成生效的协作空间，只有该协作空间内的故障才可以同步至 Jira 中。
+- **严重程度映射**：如果选择的事务类型不支持优先级字段，则无法配置该映射关系。
+- **自定义字段映射**：可以选择将故障的某些标签或所有标签以及自定义字段内容同步至 Jira 的字段中（仅支持文本类型的字段）。
+
+### 3. 关于更新
+
+- 已经创建 Issue 的故障，如果您更新了故障的严重程度、状态，Jira 中会自动更新，但 Jira 中的更新不会同步到 Flashduty 中。
+- 评论信息会同步到 Jira 中，但 Jira 中更新的内容不会同步到 Flashduty 中。
+- 更新故障中的标题、描述、标签等字段的信息，Jira 中不会更新。
+
+
+### 4. Flashduty 与 Jira 的映射关系
+
+#### 字段映射
+
+| Jira |  Flashduty | 
+| ---------- | -------- | 
+|  摘要  | 标题 | 
+| 描述   | 描述  | 
+| 优先级 | 严重程度 | 
+| 报告人 | 集成配置的用户 | 
+| 评论 | 评论 | 
+
+
+#### 状态映射
+
+| Jira |  Flashduty | 
+| ---------- | -------- | 
+|  Todo  | 待处理 | 
+|  In Progress  | 处理中 | 
+|  Done  | 已解决 | 
+
+
+### 5. 注意事项
+
+- Flashduty 会按照默认的字段映射以及您配置的自定义字段映射进行同步信息，如果您的 Jira 事务类型中有必选的字段且没有配置映射关系，则会遇到创建 Jira Issue 失败的情况。
+- Jira 的 Issue 详情是基于项目 KEY + 编号的格式进行访问的，如果您修改了项目 KEY，可能无法通过 Flashduty 中保存的 Issue 地址进行访问，请谨慎修改项目 KEY。
+`,nn=`---
 title: "配置通知模版"
 description: "通过自定义配置模版，可以实现个性化通知内容的需求"
 date: "2024-05-10T10:00:00+08:00"
@@ -6743,12 +6858,213 @@ CloseTime | int64 | 否 | 关闭时间，EndTime 为告警恢复时间，CloseTi
 
 ## 飞书机器人
 ---
-飞书机器人仅支持发送纯文本消息。
+飞书机器人支持消息卡片，富文本和普通文本三种格式，默认模版是消息卡片格式。
 
+- msg_type 字段在消息卡片和富文本中必填，否则当成普通文本格式发送
 - 消息\`最大长度为4000字节，超出后截断发送\`；
-- 如果文本中包含\`<br>\`，渲染时会\`先删除空行，再将<br>替换为换行符\`；
 - 如果不设置自定义内容，将采用系统默认模板，仅展示关键信息：
 
+1. 消息卡片
+msg_type 必填，值为 interactive
+\`\`\`
+{
+  "msg_type": "interactive",
+  "card": {
+    "config": {
+      "wide_screen_mode": true,
+      "enable_forward": true
+    },
+    "header": {
+      "template": "{{if eq .IncidentSeverity "Critical"}}red{{else if eq .IncidentSeverity "Warning"}}orange{{else}}yellow{{end}}",
+      "title": {
+        "content": "{{fireReason .}}INC #{{.Num}} {{toHtml .Title}}",
+        "tag": "plain_text"
+      }
+    },
+    "elements": [{
+      "tag": "div",
+      "fields": [{
+          "text": {
+            "tag": "lark_md",
+            "content": "**🏢 协作空间:**{{if .ChannelName}}{{.ChannelName}}{{else}}无{{end}}"
+          }
+        },
+        {
+          "text": {
+            "tag": "lark_md",
+            "content": "**{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} 严重程度:**{{.IncidentSeverity}}"
+          }
+        },
+        {
+          "text": {
+            "tag": "lark_md",
+            "content": "**⏰ 触发时间:**{{date "2006-01-02 15:04:05" .StartTime}}{{if gt .AlertCnt 1}}"
+          }
+        },
+        {
+          "text": {
+            "tag": "lark_md",
+            "content": "**🔔 聚合告警:**{{.AlertCnt}}条 {{end}}{{if .Labels.resource}}"
+          }
+        },
+        {
+          "tag": "div",
+          "text": {
+            "tag": "lark_md",
+            "content": "**📌 告警对象:**{{toHtml (joinAlertLabels . "resource" ",")}} {{end}}{{if .Description}}"
+          }
+        },
+        {
+          "tag": "div",
+          "text": {
+            "tag": "lark_md",
+            "content": "**🔍 故障描述:**{{.Description}}{{end}}{{if gt (len .Responders) 0}}"
+          }
+        },
+        {
+          "tag": "div",
+          "text": {
+            "tag": "lark_md",
+            "content": "**👨‍💻 处理人员:**{{range .Responders}}@{{.PersonName}} {{end}}{{end}}"
+          }
+        }
+      ]
+    },
+    {
+      "tag": "hr"
+    },
+    {
+      "tag": "action",
+      "actions": [{
+          "tag": "button",
+          "text": {
+            "tag": "plain_text",
+            "content": "故障详情"
+          },
+          "type": "primary",
+          "url": "{{.DetailUrl}}"
+        },
+        {
+          "tag": "button",
+          "text": {
+            "tag": "plain_text",
+            "content": "认领"
+          },
+          "type": "primary",
+          "url": "{{.DetailUrl}}?ack=1"
+        }
+      ]
+    }]
+  }
+}
+\`\`\`
+
+2. 富文本
+msg_type 必填，值为 post
+\`\`\`
+{
+    "msg_type": "post",
+    "post": {
+        "zh_cn": {
+            "title": "{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} {{fireReason .}}INC #{{.Num}} {{toHtml .Title}}",
+            "content": [
+                [{
+                    "tag": "text",
+                    "text": "🏢 "
+                }, {
+                    "tag": "text",
+                    "text": "协作空间：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{if .ChannelName}}{{.ChannelName}}{{else}}无{{end}}\\n"
+                }],
+                [{
+                    "tag": "text",
+                    "text": "{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} "
+                }, {
+                    "tag": "text",
+                    "text": "严重程度：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{.IncidentSeverity}}\\n",
+                    "text_type": "{{if eq .IncidentSeverity "Critical"}}bold{{end}}"
+                }],
+                [{
+                    "tag": "text",
+                    "text": "⏰ "
+                }, {
+                    "tag": "text",
+                    "text": "触发时间：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{date "2006-01-02 15:04:05" .StartTime}}\\n"
+                }],
+                {{if gt .AlertCnt 1}}[{
+                    "tag": "text",
+                    "text": "🔔 "
+                }, {
+                    "tag": "text",
+                    "text": "聚合告警：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{.AlertCnt}}条\\n"
+                }],{{end}}
+                {{if .Labels.resource}}[{
+                    "tag": "text",
+                    "text": "📋 "
+                }, {
+                    "tag": "text",
+                    "text": "告警对象：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{toHtml (joinAlertLabels . "resource" ", ")}}\\n"
+                }],{{end}}
+                {{if .Description}}[{
+                    "tag": "text",
+                    "text": "📝 "
+                }, {
+                    "tag": "text",
+                    "text": "描述：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{toHtml .Description}}\\n"
+                }],{{end}}
+                {{if gt (len .Responders) 0}}[{
+                    "tag": "text",
+                    "text": "👨‍💻 "
+                }, {
+                    "tag": "text",
+                    "text": "处理人员：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{range .Responders}}@{{.PersonName}} {{end}}\\n"
+                }],{{end}}
+                [{
+                    "tag": "a",
+                    "href": "{{.DetailUrl}}",
+                    "text": "故障详情"
+                },{
+                    "tag": "text",
+                    "text": "  "
+                },{
+                    "tag": "a",
+                    "href": "{{.DetailUrl}}?ack=1",
+                    "text": "认领"
+                }]
+            ]
+        }
+    }
+}
+\`\`\`
+
+3. 普通文本
 \`\`\`
 {{fireReason .}}INC #{{.Num}} {{toHtml .Title}}
 -----
@@ -7076,4 +7392,4 @@ CloseTime | int64 | 否 | 关闭时间，EndTime 为告警恢复时间，CloseTi
 <img src="https://download.flashcat.cloud/flashduty/changelog/20230720/email_render.png" alt="drawing" style="display: block; margin: 0 auto;" width="500"/>
 
 </div>
-`,nn={CustomAlert:n,Email:t,N9e:e,Prometheus:a,Grafana:i,Zabbix:s,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:o,AliyunCm:r,AliyunSLS:c,AWSCW:u,AzureMonitor:h,BaiDuBCM:m,HuaWeiCES:p,InfluxDB:g,OpenFalcon:y,PagerDuty:f,TencentBK:b,TencentCLS:v,TencentCm:w,TencentEb:_,OceanBase:k,Graylog:F,Skywalking:x,Sentry:T,Jiankongbao:A,AWSEventBridge:S,Dynatrace:C,HuaweiyunLTS:L,GoogleCM:I,Splunk:D,AppDynamics:P,SolarWinds:M,VolcEngineMetric:N,VolcEngineEvent:E,VolcEngineTLS:$,OpManager:R,Meraki:W,Zilliz:j,StateCloud:z,Guance:U,CustomChange:O,Jira:q,Lark:B,Dingtalk:G,Wecom:V,Slack:Z,MicrosoftTeams:K,AlertWebhook:J,IncidentWebhook:X,CustomAction:Q,Templates:Y,HuaweiyunAPM:H};module.exports=nn;
+`,tn={CustomAlert:n,Email:t,N9e:e,Prometheus:a,Grafana:i,Zabbix:s,UptimeKuma:l,AliyunARMS:d,AliyunCmEvent:o,AliyunCm:r,AliyunSLS:c,AWSCW:u,AzureMonitor:h,BaiDuBCM:m,HuaWeiCES:p,InfluxDB:g,OpenFalcon:y,PagerDuty:f,TencentBK:b,TencentCLS:v,TencentCm:w,TencentEb:_,OceanBase:k,Graylog:F,Skywalking:x,Sentry:T,Jiankongbao:A,AWSEventBridge:C,Dynatrace:S,HuaweiyunLTS:I,GoogleCM:L,Splunk:D,AppDynamics:P,SolarWinds:M,VolcEngineMetric:N,VolcEngineEvent:E,VolcEngineTLS:$,OpManager:R,Meraki:W,Zilliz:U,StateCloud:z,Guance:j,CustomChange:O,Jira:q,Lark:B,Dingtalk:J,Wecom:G,Slack:V,MicrosoftTeams:K,AlertWebhook:Z,IncidentWebhook:X,CustomAction:Y,Templates:nn,HuaweiyunAPM:H,JiraSync:Q};module.exports=tn;

package/dist/iife/en.js

@@ -5480,6 +5480,7 @@ The following event types are currently supported, with more potentially being a
 |    i_rslv    | Close incident (automatically or manually) |
 |   i_reopen   | Reopen incident |
 |   i_merge    | Manually merge incidents |
+|   i_comm     | Add comment |
 |  i_r_title   | Update incident title |
 |   i_r_desc   | Update incident description |
 |  i_r_impact  | Update incident impact |
@@ -6640,4 +6641,86 @@ When you need to route alerts to different channels based on alert payload infor
 
 </div>
 
+`,JiraSync:`---
+title: "Jira Sync"
+description: "Sync incidents with Jira issues through Jira Sync Webhook."
+date: "2024-05-11T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/en/flashduty/jira-sync"
+---
+
+Through Jira Sync Webhook, you can associate and synchronize Flashduty incidents with Jira Issues, enabling integration between Flashduty and Jira.
+
+## Prerequisites
+- This integration is compatible with Jira Cloud, as well as versions 7.x and 8.x of Jira Server and Jira Data Center.
+- Currently, only one-way synchronization of incident information and status to Jira is supported. Information in Jira will not sync back to Flashduty.
+- For Jira Cloud, use an API Token in the password field during authorization configuration; for Jira Server or Data Center, use your Jira account password.
+
+## Getting API Token in Jira Cloud （Jira Server and Data Center please skip）
+
+- After logging into Jira Cloud, click your profile picture 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 an API token name and select an expiration time.
+- Click **Create** to generate the API token.
+- Copy the API token value and paste it into the API token field in Flashduty's authorization configuration.
+
+## Configuring Integration in Flashduty
+
+### 1. Create and Authenticate Jira Integration
+<div class="hide">
+
+In the Integration Center, select **Webhook**, choose **Jira Sync** integration, and fill in the following authentication information.
+
+</div>
+
+- **Jira Platform Type**: Choose based on your version. For Data Center version, select Self-hosted (Server).
+- **Service URL**: For Cloud version, enter your actual access URL, e.g., https://your-domain.atlassian.net. For Server version, enter your service access URL, 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 username.
+- **API Token/Password**: Your Jira account credentials. For Cloud version, enter API Token; for Server version, enter your Jira account password.
+- After completion, click **Next** to proceed with configuration.
+
+**About Permissions**: Ensure your Jira account has permissions to access relevant projects, issue types, and create issues. Using an administrator account is recommended.
+
+### 2. Jira Integration Configuration
+
+- **Integration Name**: Define a name for this integration.
+- **Trigger Mode**:
+    - Automatic: Configure conditions for Flashduty to automatically sync qualifying incidents to Jira.
+    - Manual: Manually trigger Jira sync from the incident details page's more actions menu (integration name serves as trigger name).
+- **Project ID**: Select the target Jira project for synchronization.
+- **Issue Type**: Select the target Jira issue type.
+- **Channel**: Select the channel where this integration will be active. Only incidents within this channel can sync to Jira.
+- **Severity Mapping**: If the selected issue type doesn't support priority fields, this mapping cannot be configured.
+- **Custom Field Mapping**: Choose to sync certain or all incident labels and custom field content to Jira fields (text type fields only).
+
+### 3. About Updates
+
+- For incidents with existing Jira issues, updates to severity or status will automatically update in Jira, but Jira updates won't sync back to Flashduty.
+- Comments sync to Jira, but Jira comments won't sync back to Flashduty.
+- Updates to incident title, description, labels, or other fields won't update in Jira.
+
+### 4. Flashduty to Jira Mapping
+
+#### Field Mapping
+
+| Jira | Flashduty |
+| ---------- | -------- |
+| Summary | Title |
+| Description | Description |
+| Priority | Severity |
+| Reporter | Integration configured user |
+| Comments | Comments |
+
+#### Status Mapping
+
+| Jira | Flashduty |
+| ---------- | -------- |
+| Todo | Pending |
+| In Progress | In Progress |
+| Done | Resolved |
+
+### 5. Important Notes
+
+- Flashduty syncs information according to default field mappings and your custom field configurations. If your Jira issue type has required fields without mapping relationships, Jira issue creation may fail.
+- Jira issue details are accessed using project KEY + number format. If you modify the project KEY, saved issue URLs in Flashduty may become inaccessible, so please modify project KEYs with caution.
 `};n.FlashDocsEn=u})(window);

package/dist/iife/zh.js

@@ -5144,13 +5144,33 @@ sidebarDepth: 3
     - 确保账户已经完成关联，前往 飞书 > 工作台 > 搜索应用名称 > 打开应用，完成一次登录并关联（飞书< - >Flashduty）账号。如果已经登录过，尝试点击右上角菜单，切换账户，重新登录来绑定账号
     - 确保已购买足够的 license，已使用 license 情况，可以在控制台 > 费用中心查看
 
-2. **分派策略飞书群聊列表为空**？
+3. **分派策略飞书群聊列表为空**？
 
     - 前往 飞书，选择群聊会话，添加已创建的Flashduty机器人，如下图所示：
     - 回到分派策略配置页面，刷新后重新选择群聊列表
 
 <img alt="drawing" width="800" src="https://download.flashcat.cloud/feishu-self-app-invite-to-chat.jpeg" />
 <img src="https://download.flashcat.cloud/feishu-self-app-notify-rule.png" alt="drawing" width="800"/>
+
+4. **飞书自建应用 API 限制：** [飞书文档说明](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/platform-updates-/custom-app-api-call-limit)
+
+    **调用量限制：**
+
+    |     飞书版本     | 调用总量/月 | 刷新时间  |                       
+    | :----------: | :--: | :----: |
+    |基础免费版|10,000 次|每个自然月的 1 号|
+    |其他版本|不限制|-|        
+
+    **频控限制：**
+
+    |    场景     | 限制 |                   
+    | :----------: | :--: | 
+    |所有接口|每个应用最高频率 50 次/秒|
+    |发消息接口|每个应用最高频率 1000 次/分钟|
+    |群机器人 Webhook|最高频率 100 次/分钟|
+    |给同一个用户或同一个群发消息|最高频率 5 次/秒|
+
+    **注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
 `,Dingtalk:`---
 title: "钉钉集成"
 description: "通过集成钉钉自建应用，实现在钉钉端内接收和响应告警的能力"
@@ -5302,6 +5322,15 @@ url: "https://docs.flashcat.cloud/zh/flashduty/dingtalk-integration-guide"
 
 <img src="https://download.flashcat.cloud/dingtalk-self-app-notify-rule.png" alt="drawing" width="800"/>
 
+4. **钉钉自建应用 API 调用量：** [钉钉文档说明](https://open.dingtalk.com/document/orgapp/descriptions-about-adjusting-limit-and-frequency-of-api-calls?spm=ding_open_doc.document.0.0.6f6b21d9WtkxJI)
+
+|     钉钉版本     | 调用总量/月 | QPS| 刷新时间  |                       
+| :----------: | :--: | :----: | :----:|
+|标准版|10,000 次|20|每月1日|
+|专业版|50万次|40|     每月1日          |
+|专属版|550万次|60|     每月1日          |
+
+**注意：** 超出限制后将无法正常推送消息，建议合理使用通知渠道
 `,Wecom:`---
 title: "企业微信集成"
 description: "通过集成企业微信第三方应用，实现在企业微信端内接收和响应告警的能力"
@@ -5722,6 +5751,7 @@ curl -X POST 'https://example.com/alert/webhook?a=a' \\
 |    i_rslv    | 关闭故障（自动或手动关闭） |
 |   i_reopen   | 重新打开故障     |
 |   i_merge    | 手动合并故障     |
+|   i_comm     | 添加评论     |
 |  i_r_title   | 更新故障标题     |
 |   i_r_desc   | 更新故障描述     |
 |  i_r_impact  | 更新故障影响     |
@@ -6635,12 +6665,213 @@ CloseTime | int64 | 否 | 关闭时间，EndTime 为告警恢复时间，CloseTi
 
 ## 飞书机器人
 ---
-飞书机器人仅支持发送纯文本消息。
+飞书机器人支持消息卡片，富文本和普通文本三种格式，默认模版是消息卡片格式。
 
+- msg_type 字段在消息卡片和富文本中必填，否则当成普通文本格式发送
 - 消息\`最大长度为4000字节，超出后截断发送\`；
-- 如果文本中包含\`<br>\`，渲染时会\`先删除空行，再将<br>替换为换行符\`；
 - 如果不设置自定义内容，将采用系统默认模板，仅展示关键信息：
 
+1. 消息卡片
+msg_type 必填，值为 interactive
+\`\`\`
+{
+  "msg_type": "interactive",
+  "card": {
+    "config": {
+      "wide_screen_mode": true,
+      "enable_forward": true
+    },
+    "header": {
+      "template": "{{if eq .IncidentSeverity "Critical"}}red{{else if eq .IncidentSeverity "Warning"}}orange{{else}}yellow{{end}}",
+      "title": {
+        "content": "{{fireReason .}}INC #{{.Num}} {{toHtml .Title}}",
+        "tag": "plain_text"
+      }
+    },
+    "elements": [{
+      "tag": "div",
+      "fields": [{
+          "text": {
+            "tag": "lark_md",
+            "content": "**🏢 协作空间:**{{if .ChannelName}}{{.ChannelName}}{{else}}无{{end}}"
+          }
+        },
+        {
+          "text": {
+            "tag": "lark_md",
+            "content": "**{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} 严重程度:**{{.IncidentSeverity}}"
+          }
+        },
+        {
+          "text": {
+            "tag": "lark_md",
+            "content": "**⏰ 触发时间:**{{date "2006-01-02 15:04:05" .StartTime}}{{if gt .AlertCnt 1}}"
+          }
+        },
+        {
+          "text": {
+            "tag": "lark_md",
+            "content": "**🔔 聚合告警:**{{.AlertCnt}}条 {{end}}{{if .Labels.resource}}"
+          }
+        },
+        {
+          "tag": "div",
+          "text": {
+            "tag": "lark_md",
+            "content": "**📌 告警对象:**{{toHtml (joinAlertLabels . "resource" ",")}} {{end}}{{if .Description}}"
+          }
+        },
+        {
+          "tag": "div",
+          "text": {
+            "tag": "lark_md",
+            "content": "**🔍 故障描述:**{{.Description}}{{end}}{{if gt (len .Responders) 0}}"
+          }
+        },
+        {
+          "tag": "div",
+          "text": {
+            "tag": "lark_md",
+            "content": "**👨‍💻 处理人员:**{{range .Responders}}@{{.PersonName}} {{end}}{{end}}"
+          }
+        }
+      ]
+    },
+    {
+      "tag": "hr"
+    },
+    {
+      "tag": "action",
+      "actions": [{
+          "tag": "button",
+          "text": {
+            "tag": "plain_text",
+            "content": "故障详情"
+          },
+          "type": "primary",
+          "url": "{{.DetailUrl}}"
+        },
+        {
+          "tag": "button",
+          "text": {
+            "tag": "plain_text",
+            "content": "认领"
+          },
+          "type": "primary",
+          "url": "{{.DetailUrl}}?ack=1"
+        }
+      ]
+    }]
+  }
+}
+\`\`\`
+
+2. 富文本
+msg_type 必填，值为 post
+\`\`\`
+{
+    "msg_type": "post",
+    "post": {
+        "zh_cn": {
+            "title": "{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} {{fireReason .}}INC #{{.Num}} {{toHtml .Title}}",
+            "content": [
+                [{
+                    "tag": "text",
+                    "text": "🏢 "
+                }, {
+                    "tag": "text",
+                    "text": "协作空间：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{if .ChannelName}}{{.ChannelName}}{{else}}无{{end}}\\n"
+                }],
+                [{
+                    "tag": "text",
+                    "text": "{{if eq .IncidentSeverity "Critical"}}🔴{{else if eq .IncidentSeverity "Warning"}}⚠️{{else}}ℹ️{{end}} "
+                }, {
+                    "tag": "text",
+                    "text": "严重程度：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{.IncidentSeverity}}\\n",
+                    "text_type": "{{if eq .IncidentSeverity "Critical"}}bold{{end}}"
+                }],
+                [{
+                    "tag": "text",
+                    "text": "⏰ "
+                }, {
+                    "tag": "text",
+                    "text": "触发时间：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{date "2006-01-02 15:04:05" .StartTime}}\\n"
+                }],
+                {{if gt .AlertCnt 1}}[{
+                    "tag": "text",
+                    "text": "🔔 "
+                }, {
+                    "tag": "text",
+                    "text": "聚合告警：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{.AlertCnt}}条\\n"
+                }],{{end}}
+                {{if .Labels.resource}}[{
+                    "tag": "text",
+                    "text": "📋 "
+                }, {
+                    "tag": "text",
+                    "text": "告警对象：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{toHtml (joinAlertLabels . "resource" ", ")}}\\n"
+                }],{{end}}
+                {{if .Description}}[{
+                    "tag": "text",
+                    "text": "📝 "
+                }, {
+                    "tag": "text",
+                    "text": "描述：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{toHtml .Description}}\\n"
+                }],{{end}}
+                {{if gt (len .Responders) 0}}[{
+                    "tag": "text",
+                    "text": "👨‍💻 "
+                }, {
+                    "tag": "text",
+                    "text": "处理人员：",
+                    "text_type": "bold"
+                }, {
+                    "tag": "text",
+                    "text": "{{range .Responders}}@{{.PersonName}} {{end}}\\n"
+                }],{{end}}
+                [{
+                    "tag": "a",
+                    "href": "{{.DetailUrl}}",
+                    "text": "故障详情"
+                },{
+                    "tag": "text",
+                    "text": "  "
+                },{
+                    "tag": "a",
+                    "href": "{{.DetailUrl}}?ack=1",
+                    "text": "认领"
+                }]
+            ]
+        }
+    }
+}
+\`\`\`
+
+3. 普通文本
 \`\`\`
 {{fireReason .}}INC #{{.Num}} {{toHtml .Title}}
 -----
@@ -7076,4 +7307,89 @@ url: "https://docs.flashcat.cloud/zh/flashduty/huawei-apm-integration-guide"
 
 </div>
 
+`,JiraSync:`---
+title: "Jira 同步"
+description: "通过 Jira 同步 Webhook，实现故障与 Jira Issue 的关联。"
+date: "2024-05-11T10:00:00+08:00"
+url: "https://docs.flashcat.cloud/zh/flashduty/jira-sync"
+---
+
+通过 Jira 同步 Webhook，将 Flashduty 的故障与 Jira Issue 进行关联同步，实现 Flashduty 与 Jira 的联动。
+
+## 前提说明
+- 该集成兼容 Jira Cloud 以及 Jira Server 和 Jira Data Center 的 7.x 和 8.x 版本。
+- 目前仅支持将故障相关信息或状态单向同步到 Jira 中，Jira 中的信息不会同步到 Flashduty 中。
+- 对于 Jira Cloud，请在授权配置的密码处填写 API Token；而对于Jira Server 或 Data Center，则使用您的 Jira 账户登录密码即可。
+
+## 在 Jira Cloud 中获取 API Token （Jira Server 和 Data Center 请跳过）
+
+- 登录 Jira Cloud 后，点击右上角头像，选择 **管理账户**。
+- 在 **管理账户** 页面中，选择 **安全性** 选项卡。
+- 在 **安全性** 页面中，点击 **创建并管理 API 令牌** 按钮。
+- 在 **创建并管理 API 令牌** 弹窗中，填写 API token 名称，并选择过期时间。
+- 点击 **创建** 按钮，创建 API token。
+- 创建完成后，复制 API token 值，并粘贴到 Flashduty 授权配置中的 API 令牌处。
+
+## 在 Flashduty 中配置集成
+
+### 1. 创建并认证 Jira 集成
+<div class="hide">
+
+在集成中心，选择 **Webhook** ，选择 **Jira 同步** 集成，并填写以下认证信息。
+
+</div>
+
+- **Jira 平台类型**：根据您使用的版本进行选择，如果是 Data Center 版本的请选择私有化（Server） 即可。
+- **服务地址**：Cloud 版本请填写您的实际访问地址，例如： https://your-domain.atlassian.net，Server 版本请填写您的服务访问地址，例如： https://your-jira-server-url.com。
+- **用户名**：您的 Jira 账户名，Cloud 版本请填写您的邮箱，Server 版本请填写您的 Jira 账户名。
+- **API令牌/密码**：您的 Jira 账户密码，Cloud 版本请填写 API Token，Server 版本请填写您的 Jira 账户密码。
+- 填写完成后，点击 **下一步** 按钮，进行相关配置。
+
+**关于权限**：请确保您的 Jira 账户拥有获取相关项目、事务类型以及创建 Issue 等权限，建议使用管理员账户。
+
+### 2. Jira 集成配置
+
+- **集成名称**：为当前集成定义一个名称。
+- **触发模式**：
+    - 自动触发：需要配置相应的条件，Flashduty 会自动将符合条件的故障同步到 Jira 中。
+    - 手动触发：需要在故障详情页的更多操作中手动触发 Jira 同步（该集成配置的名称为触发器名称）。
+- **项目 ID**：选择需要同步至 Jira 的项目。
+- **事务类型**：选择需要同步至 Jira 的事务类型。
+- **协作空间**：选择该集成生效的协作空间，只有该协作空间内的故障才可以同步至 Jira 中。
+- **严重程度映射**：如果选择的事务类型不支持优先级字段，则无法配置该映射关系。
+- **自定义字段映射**：可以选择将故障的某些标签或所有标签以及自定义字段内容同步至 Jira 的字段中（仅支持文本类型的字段）。
+
+### 3. 关于更新
+
+- 已经创建 Issue 的故障，如果您更新了故障的严重程度、状态，Jira 中会自动更新，但 Jira 中的更新不会同步到 Flashduty 中。
+- 评论信息会同步到 Jira 中，但 Jira 中更新的内容不会同步到 Flashduty 中。
+- 更新故障中的标题、描述、标签等字段的信息，Jira 中不会更新。
+
+
+### 4. Flashduty 与 Jira 的映射关系
+
+#### 字段映射
+
+| Jira |  Flashduty | 
+| ---------- | -------- | 
+|  摘要  | 标题 | 
+| 描述   | 描述  | 
+| 优先级 | 严重程度 | 
+| 报告人 | 集成配置的用户 | 
+| 评论 | 评论 | 
+
+
+#### 状态映射
+
+| Jira |  Flashduty | 
+| ---------- | -------- | 
+|  Todo  | 待处理 | 
+|  In Progress  | 处理中 | 
+|  Done  | 已解决 | 
+
+
+### 5. 注意事项
+
+- Flashduty 会按照默认的字段映射以及您配置的自定义字段映射进行同步信息，如果您的 Jira 事务类型中有必选的字段且没有配置映射关系，则会遇到创建 Jira Issue 失败的情况。
+- Jira 的 Issue 详情是基于项目 KEY + 编号的格式进行访问的，如果您修改了项目 KEY，可能无法通过 Flashduty 中保存的 Issue 地址进行访问，请谨慎修改项目 KEY。
 `};n.FlashDocsZh=t})(window);

package/dist/zh.d.ts

@@ -53,5 +53,6 @@ declare const docs: {
     CustomAction: string;
     Templates: string;
     HuaweiyunAPM: string;
+    JiraSync: string;
 };
 export default docs;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flashduty-knowledge-base",
-  "version": "1.2.4-beta.5",
+  "version": "1.2.5",
   "description": "flashduty knowledge base",
   "type": "module",
   "scripts": {