Merge pull request #284 from flashcatcloud/doc-review/2026-08-19-083500

docs: doc-review 2026-08-19 — incident timeline, alert detail deep links, email limit, ai-sre updates

Author: ysyneu

en/ai-sre/artifacts.mdx

@@ -58,7 +58,7 @@ Clicking the card body opens the artifact's detail page. Hovering over a card re
 
 Click **New artifact** in the upper-right corner of the page to jump to the chat page with a prefilled draft prompt:
 
-> I want to build a publishable Artifact in Flashduty AI-SRE: a self-contained web page or report published with the publish_artifact tool. Ask me a few focused questions about the audience, content/data, interactions, and visual style, then build it and publish it.
+> I want to build a publishable Artifact in Flashduty AI-SRE: a self-contained web page or report, published to the artifact gallery when done. Ask me a few focused questions about the audience, content/data, interactions, and visual style, then build it and publish it.
 
 The agent first asks you about the target audience, content/data source, interactions, and visual style, then builds and publishes the artifact — there is no form to fill out directly.
 

en/ai-sre/sessions.mdx

@@ -115,6 +115,8 @@ Opening a session clears its unread dot.
 
 Type a message in the input box at the bottom and press Enter to send. The input box supports Markdown and slash commands (type `/` to open the command menu) to trigger built-in skills and commands.
 
+When the console publishes a new version, a **version update notice** appears above the input box: "A new version of the console has been published. Refresh the page to continue." Click **Refresh** to reload the page and use the new version; clicking the close button hides the notice, and it will not repeat for the same version (the notice only appears in the full web console, not in embedded mode or on-premises deployments).
+
 ### Attachments and Context References
 
 <AccordionGroup>

en/changelog/changelog.mdx

@@ -4,6 +4,26 @@ description: "This page documents important updates and feature releases for Fla
 keywords: ["Changelog", "Product Release", "Feature Updates", "Flashduty", "Version History"]
 ---
 
+<Update label="2026-08-19" description="🕒 Incident timeline and alert details experience updates">
+
+### Incident timeline redesign
+
+The incident timeline has been visually and interactively upgraded:
+
+- Each record now shows the full date and time (`YYYY-MM-DD HH:mm:ss`) by default; hovering switches to a relative time (e.g. "3 minutes ago"). Day-separator rows are no longer inserted
+- New rendering for **reassignment** and **responder-change** events: reassignments (assign or reassign a new responder) and responder changes (updated the responder to) are written into the timeline with member names instead of falling back to the generic display
+- Images in comments and records now open the original image in a new tab when clicked (no more in-page preview)
+
+### Alert details tab deep link
+
+The active tab on the alert details page is controlled by the URL parameter `tab`: appending `?tab=events` to the alert details URL opens the **Associated Events** tab directly, and tab switches are synced to the browser address bar. The **View full event history** entry in the "showing only the latest N alert events" hint on the incident details page uses this mechanism.
+
+### Label quick-jump enhancement
+
+The **View Rule** deep link for `monit.alert` integration labels now recognizes both `rule_id` and `__alert_rule_id` (new data prefers the latter), and renders the link only when the label value is a positive integer; empty or non-numeric values degrade to plain text.
+
+</Update>
+
 <Update label="2026-08-18" description="🔧 Kubernetes App permission details update and quick-silence label exclusion rules">
 
 ### Kubernetes App permission details update

en/on-call/incident/alert-management.mdx

@@ -100,6 +100,8 @@ The details page body is split into two tabs:
 | **Alert Overview** | The left side shows the alert description, labels, and **related events preview** (up to 5 entries, with a link to the *Associated Events* tab for the full list); the right side shows attributes (channel, trigger time), images, alert source, associated incident, and Links |
 | **Associated Events** | Shows the list of all raw events associated with this alert |
 
+The active tab is controlled by the URL parameter `tab`: appending `?tab=events` to the alert details URL (e.g. `/alert/detail/{id}?tab=events`) opens the **Associated Events** tab directly, and tab switches are synced to the address bar. The **View full event history** entry in the "showing only the latest N alert events" hint on the incident details page uses this mechanism.
+
 The **Alert Source** is clickable so you can quickly trace where an alert came from:
 
 - **Alerts from the Monit integration**: Display the name of the rule that produced the alert. Click to jump to that alert rule — Entity Tree rules open the rule editing view directly in Entity Tree, while standalone rules open the rule details page. When older data lacks rule labels, it falls back to showing the integration name and links to the integration details

en/on-call/incident/search-view-incident.mdx

@@ -112,9 +112,10 @@ Incident labels are displayed in the **Details** area of the details page. When
 | :--- | :--- | :--- |
 | `rum.alert` | `issue_id` | A **View Issue** link is rendered next to the label value, jumping to the corresponding issue in RUM error tracking |
 | `monit.alert` | `rule_id` | A **View Rule** link is rendered next to the label value, jumping to the standalone alert rule that generated the alert |
+| `monit.alert` | `__alert_rule_id` | A **View Rule** link is rendered next to the label value, jumping to the standalone alert rule that generated the alert. New data prefers this label; historical data falls back to `rule_id` |
 | `monit.alert` | `__entity_alert_rule_id` | A **View Rule** link is rendered next to the label value, jumping to the edit view of the corresponding alert rule in the entity tree |
 
-Jumping to an entity-tree rule requires contextual labels such as `__entity_alert_account_id`, `__entity_alert_entity_definition_id`, `__entity_alert_data_source_id`, and `__entity_alert_policy_scope_group_id` for locating; when any required label is missing or invalid, the label value is shown as plain text. This deep-link capability also applies to the label area of the alert details page.
+Jumping to an entity-tree rule requires contextual labels such as `__entity_alert_account_id`, `__entity_alert_entity_definition_id`, `__entity_alert_data_source_id`, and `__entity_alert_policy_scope_group_id` for locating; when any required label is missing or invalid, the label value is shown as plain text. Standalone alert rules (`rule_id` / `__alert_rule_id`) likewise require a positive integer value (e.g. `123`); when the value is empty, `0`, or non-numeric, the label is shown as plain text to avoid generating an invalid link. This deep-link capability also applies to the label area of the alert details page.
 
 ### Detail Tabs
 
@@ -124,7 +125,7 @@ The incident details page contains 7 tabs; some appear only under certain condit
 | :--- | :--- | :--- |
 | **Incident Overview** | A panoramic view including the incident summary, key attributes, recent timeline, responders, and associated events. This is the default tab when the details page opens | Always visible |
 | **Associated Alerts** | All [grouped](/en/on-call/channel/noise-reduction) alerts associated with the incident, with filtering by progress and view switching | Visible only when `alert_cnt > 0` |
-| **Timeline** | The complete lifecycle record of the incident — triggering, assignment, notifications, acknowledgments, snoozes, closure, comments, and action-item and follow-up operations such as creation, updates, and completion — with a Markdown comment box at the top | Always visible |
+| **Timeline** | The complete lifecycle record of the incident — triggering, assignment, reassignment, responder changes, notifications, acknowledgments, snoozes, closure, comments, and action-item and follow-up operations such as creation, updates, and completion — with a Markdown comment box at the top | Always visible |
 | **Change History** | Change events correlated with the current incident in time, helping you pinpoint the relationship between the incident and recent deployments or configuration changes | Always visible |
 | **Resolution** | Structured fields recording the incident's impact, root cause, and resolution | Visible only when the incident has any of `impact` / `root_cause` / `resolution` |
 | **Postmortem** | A built-in postmortem editor that lets you create, edit, AI-generate, and publish a postmortem report without leaving the details page | Subject to subscription tier; always visible when enabled |
@@ -150,6 +151,7 @@ The top of the Timeline tab provides a Markdown comment box that supports:
 
 - Writing notes, troubleshooting memos, or meeting summaries in Markdown syntax
 - Pasting or uploading images directly; screenshots are auto-uploaded and converted into image links
+- Clicking an image in a comment opens the original image in a new tab (no in-page preview)
 - Mentioning members with @ in a comment — the mentioned member receives a dedicated personal notification (with the comment content and an incident link, delivered by email and Flashduty App push by default), making it easy to pull the right people into the discussion
 - Appending the published comment as a record on the incident timeline, interleaved with system-generated events for easy retrospection
 

en/on-call/incident/what-is-incident.mdx

@@ -117,6 +117,8 @@ Flashduty On-call currently doesn't restrict incidents to only be acknowledged b
 
 Every incident has a timeline for tracing changes and actions at different historical moments. For example, at what time, through what channel, who was notified, and notification results.
 
+Each timeline record shows the full date and time (`YYYY-MM-DD HH:mm:ss`) by default; hovering switches to a relative time (e.g. "3 minutes ago").
+
 <Frame>
 <img src="https://download.flashcat.cloud/flashduty/kb/timeline.png" alt="Incident Timeline" />
 </Frame>

en/on-call/integration/alert-integration/alert-sources/email.mdx

@@ -74,7 +74,7 @@ By default, the system creates a new alert for every email, but you can switch t
 ### Important Notes
 
 1. The system will reject emails larger than 5MB
-2. If the email text content exceeds 32KB, the system will truncate it and add a label in the incident details:
+2. If the email text content exceeds 128KB, the system will truncate it and add a label in the incident details:
 
 ```
 body_cut = true

zh/ai-sre/artifacts.mdx

@@ -58,7 +58,7 @@ sidebarTitle: 产物
 
 点击页面右上角的 **新建产物**，会跳转到会话页面并预填一段引导草稿：
 
-> 我想在 Flashduty AI-SRE 中创建一个可发布的产物：一个用 publish_artifact 工具发布的自包含网页或报告。请先问我几个必要问题，包括目标读者、内容/数据、交互和视觉风格，然后构建并发布它。
+> 我想在 Flashduty AI-SRE 中创建一个可发布的产物：一个自包含的网页或报告，完成后发布到产物库。请先问我几个必要问题，包括目标读者、内容/数据、交互和视觉风格，然后构建并发布它。
 
 Agent 会先向你确认目标读者、内容/数据来源、交互与视觉风格等细节，再动手构建并发布，而不是打开一个表单直接创建。
 

zh/ai-sre/sessions.mdx

@@ -115,6 +115,8 @@ Subagent / A2A 子会话本身也不能单独开启分享——分享只能在**
 
 在底部输入框输入消息后回车发送。输入框支持 Markdown，并支持以斜杠命令（输入 `/` 调出命令菜单）触发内置 Skill 与命令。
 
+当控制台发布了新版本时，输入框上方会显示一条**版本更新提示**：「控制台已发布新版本，刷新页面后继续」。点击 **刷新** 会重新加载页面以使用新版本；点击关闭按钮可隐藏提示，同一版本不再重复提示（提示仅在全功能 Web 控制台显示，嵌入模式与私有化部署不显示）。
+
 ### 附件与上下文引用
 
 <AccordionGroup>

zh/changelog/changelog.mdx

@@ -4,6 +4,26 @@ description: "本页面记录 Flashduty 产品的重要更新和功能发布"
 keywords: ["更新日志", "产品发布", "功能更新", "Flashduty", "版本记录"]
 ---
 
+<Update label="2026-08-19" description="🕒 故障时间线与告警详情体验更新">
+
+### 故障时间线视觉重构
+
+故障详情的时间线进行了视觉与交互升级：
+
+- 每条记录默认显示完整的日期时间（`YYYY-MM-DD HH:mm:ss`），鼠标悬停时切换为相对时间（如「3 分钟前」）；不再按天插入日期分隔行
+- 新增**转派**与**处理人员变更**事件的渲染：转派（分派或转派新的负责人员）与处理人员变更（更新了处理人员为）会以人员姓名写入时间线，不再落入通用展示
+- 评论与记录中的图片改为点击后在新标签页打开原图（不再提供页内预览）
+
+### 告警详情页签深链
+
+告警详情页的页签状态由 URL 参数 `tab` 控制：在告警详情地址后附加 `?tab=events` 可直达 **关联事件** 页签，页签切换也会同步到浏览器地址栏；故障详情中「仅展示最新 N 条告警事件」提示的 **查看完整事件历史** 入口即使用该方式打开。
+
+### 标签快捷跳转增强
+
+`monit.alert` 集成标签的「查看规则」深链现在同时识别 `rule_id` 与 `__alert_rule_id`（新数据优先使用后者），且仅当标签值为正整数时渲染链接，值为空或非数字时退化为纯文本展示。
+
+</Update>
+
 <Update label="2026-08-18" description="🔧 Kubernetes App 权限说明更新与快速静默标签排除规则">
 
 ### Kubernetes App 权限说明更新