Skip to content

docs: 修掉两处悬空锚点 —— sla-and-escalation 指向 automation 的 Flows 一节，zh 版 mobile 的 roadmap 去锚点 #868

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yinlianghui merged 1 commit into from
Aug 6, 2026
Merged

docs: 修掉两处悬空锚点 —— sla-and-escalation 指向 automation 的 Flows 一节，zh 版 mobile 的 roadmap 去锚点 #868

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions .changeset/dangling-anchors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
'hotcrm': patch
---

Fix two dangling in-page anchors in the docs, so both links land on the section
they promise instead of the top of the page.

`service/sla-and-escalation` (all three locales) pointed the escalation-trigger
sentence at `/docs/administration/automation#case-escalation`. The automation
page has no *Case Escalation* heading — *Case Escalation Process* is a row in
the table under `## Flows (multi-step)`, which is where a reader chasing the
trigger condition actually has to go. The English page now links
`/docs/administration/automation#flows-multi-step`. The Chinese pages link the
page with no anchor (`/zh-Hans/docs/administration/automation`,
`/zh-Hant/docs/administration/automation`): the heading there is
「流程（多步骤）」/「流程（多步驟）」, whose slug is not `flows-multi-step`,
and un-anchored is the form already used for cross-locale links elsewhere in
the guides.

`guides/mobile` in Chinese pointed the roadmap link at
`/zh-Hans/docs/whats-new#roadmap` (and the `zh-Hant` twin). The heading on the
translated What's New pages is 「路线图」/「路線圖」 — the heading was
translated, the anchor was not — so `#roadmap` resolved to nothing. Both now
link `/zh-Hans/docs/whats-new` and `/zh-Hant/docs/whats-new`. The English
`guides/mobile` keeps `#roadmap`, which resolves to the `## Roadmap` heading it
has always had.
2 changes: 1 addition & 1 deletion content/docs/guides/mobile.zh-Hans.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ description: 在你的手机或平板上使用 HotCRM —— 哪些可用、哪

HotCRM 通过**响应式 Web 应用**在手机和平板上运行 —— 在任何现代移动浏览器中打开 `your-hotcrm-url`，你就会获得为该设备优化的布局。

> 原生 iOS / Android 应用已在[路线图](/zh-Hans/docs/whats-new#roadmap)上。
> 原生 iOS / Android 应用已在[路线图](/zh-Hans/docs/whats-new)上。

## 在移动端运行良好的功能

Expand Down
2 changes: 1 addition & 1 deletion content/docs/guides/mobile.zh-Hant.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ description: 在你的手機或平板上使用 HotCRM —— 哪些可用、哪

HotCRM 透過**響應式 Web 應用**在手機和平板上執行 —— 在任何現代行動瀏覽器中開啟 `your-hotcrm-url`，你就會獲得為該裝置最佳化的版面配置。

> 原生 iOS / Android 應用已在[路線圖](/zh-Hant/docs/whats-new#roadmap)上。
> 原生 iOS / Android 應用已在[路線圖](/zh-Hant/docs/whats-new)上。

## 在行動版執行良好的功能

Expand Down
2 changes: 1 addition & 1 deletion content/docs/service/sla-and-escalation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,5 +125,5 @@ If priority resolves to **Critical**, the Copilot immediately recommends escalat

- The SLA target per priority is set via the case object's automation (a SLA-calculation hook). To adjust, edit `src/objects/case.hook.ts` (binds to `crm_case`) or change the underlying configuration — see [Administration › Automation](/docs/administration/automation).
- Business-hours vs. calendar-hours behaviour is controlled by your tenant's business-hours setup. See [Administration › Setup](/docs/administration/setup).
- Escalation triggers (Critical, or High+Customer) live in the [Case Escalation flow definition](/docs/administration/automation#case-escalation). Adjust the condition there to change when escalation fires.
- Escalation triggers (Critical, or High+Customer) live in the [Case Escalation flow definition](/docs/administration/automation#flows-multi-step). Adjust the condition there to change when escalation fires.
- The recipient lists for *Notify on Critical* and *Notify on Escalation* are configurable in the case workflow rules.
2 changes: 1 addition & 1 deletion content/docs/service/sla-and-escalation.zh-Hans.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,5 +125,5 @@ SLA 目标可按优先级配置——参见下方的*给管理员的提示*部

- 每个优先级的 SLA 目标通过工单对象的自动化（一个 SLA 计算钩子）设置。要调整，请编辑 `src/objects/case.hook.ts`（绑定到 `crm_case`）或更改底层配置——参见 [管理 › 自动化](/zh-Hans/docs/administration/automation)。
- 营业时间与日历时间的行为由你租户的营业时间设置控制。参见 [管理 › 设置](/zh-Hans/docs/administration/setup)。
- 升级触发条件（Critical，或 High+Customer）存在于 [工单升级流程定义](/zh-Hans/docs/administration/automation#case-escalation)中。在那里调整条件即可更改升级何时触发。
- 升级触发条件（Critical，或 High+Customer）存在于 [工单升级流程定义](/zh-Hans/docs/administration/automation)中。在那里调整条件即可更改升级何时触发。
- *紧急时通知*和*升级时通知*的收件人列表可在工单工作流规则中配置。
2 changes: 1 addition & 1 deletion content/docs/service/sla-and-escalation.zh-Hant.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,5 +125,5 @@ SLA 目標可按優先順序配置——參見下方的*給管理員的提示*

- 每個優先順序的 SLA 目標透過工單物件的自動化（一個 SLA 計算鉤子）設定。要調整，請編輯 `src/objects/case.hook.ts`（綁定到 `crm_case`）或更改底層配置——參見 [管理 › 自動化](/zh-Hant/docs/administration/automation)。
- 營業時間與日曆時間的行為由你租戶的營業時間設定控制。參見 [管理 › 設定](/zh-Hant/docs/administration/setup)。
- 升級觸發條件（Critical，或 High+Customer）存在於 [工單升級流程定義](/zh-Hant/docs/administration/automation#case-escalation)中。在那裡調整條件即可更改升級何時觸發。
- 升級觸發條件（Critical，或 High+Customer）存在於 [工單升級流程定義](/zh-Hant/docs/administration/automation)中。在那裡調整條件即可更改升級何時觸發。
- *緊急時通知*和*升級時通知*的收件人列表可在工單工作流規則中配置。
Loading