Skip to content

service/index 的《Where to find things》(:63-67) 四项与 crm.app.ts 的 Service 分组三项对不上：Service Board 不存在、Tasks 不在这个组、Knowledge 被漏掉、导航项实际叫 Service Overview #927

Closed
#932
Closed
service/index 的《Where to find things》(:63-67) 四项与 crm.app.ts 的 Service 分组三项对不上：Service Board 不存在、Tasks 不在这个组、Knowledge 被漏掉、导航项实际叫 Service Overview#927
#932
Assignees
yinlianghui
Labels
documentationImprovements or additions to documentationpm:dispatchedDispatched to a dev agent by /pm-dispatch

Description

@yinlianghui
yinlianghui
opened on Aug 6, 2026

发现自 #917 / PR #924 的实施过程（核对 Service Board 这个名字的全仓落点时命中）。

基线 origin/main = 6014b2cf（含 PR #913 / #918 / #919，平台 17.0.0-rc.3）。三语同行号。

事实

content/docs/service/index.mdx:63-:67：

In the Enterprise CRM app, the **Service** group contains:

- **Cases**
- **Tasks**
- **Service Board** — kanban-style case workflow
- **Service Dashboard**

src/apps/crm.app.ts:130-140 的 group_service 实际只有三个 children：

{ id: 'nav_case',      type: 'object', objectName: 'crm_case',              label: 'Cases',     icon: 'life-buoy' },
{ id: 'nav_knowledge', type: 'object', objectName: 'crm_knowledge_article', label: 'Knowledge', icon: 'book-open' },
{ id: 'nav_service_dashboard', type: 'dashboard', dashboardName: 'service_dashboard', label: 'Service Overview', icon: 'gauge' },

逐项：

  • Cases —— ✅ 对。
  • Tasks —— ❌ 不在 Service 分组里。crm_task 的两个导航项 nav_my_tasks（My Tasks）与 nav_all_tasks（All Tasks）挂在另一个分组下（src/apps/crm.app.ts:84 / :93）。
  • Service Board —— ❌ 这个名字全仓不存在，也不是导航项。看板是视图 case_workflow，label: 'Service Workflow'（src/views/case.view.ts:72-75），要经由 Cases 的视图切换器里的 Workflow 页签（:59）进入，不在左侧导航上。
  • Service Dashboard —— ⚠️ 导航项存在，但 label 是 Service Overview，不是 Service Dashboard。
  • Knowledge（crm_knowledge_article）—— ⚠️ 真实存在于该分组，但这份清单漏掉了它。

三语同址：index.zh-Hans.mdx:66 作「服务看板——看板式工单工作流」，index.zh-Hant.mdx:66 作「服務看板——看板式工單工作流」。

为什么要紧

这一节的标题就叫《Where to find things》，是新用户找路的第一站。四项里一项名字不存在、一项分组错、一项 label 与产品里不一致，还漏了这个分组里真实存在的 Knowledge —— 照它去左侧导航上找，四次里有三次落空。

边界

Refs #917 #904 #926

Activity

  1. yinlianghui
    added
    documentationImprovements or additions to documentation
    pm:queueReady for the PM dispatch loop
    pm:dispatchedDispatched to a dev agent by /pm-dispatch
    and removed
    pm:queueReady for the PM dispatch loop
    on Aug 6, 2026
  2. yinlianghui
    self-assigned this
    on Aug 6, 2026

  3. yinlianghui commented on Aug 6, 2026

    @yinlianghui
    yinlianghui
    on Aug 6, 2026 – with Claude
    CollaboratorAuthor

    🔒 认领(/pm-dispatch R29)— session session_01VHrPAGEgFDoHjphqYG4BMa,分支 claude/issue-927-service-index-navigation。

    文件面:content/docs/service/index{,.zh-Hans,.zh-Hant}.mdx 的《Where to find things》一节(基线 :63-67)——⚠️ 本页经 #913/#922 两轮修改,fresh main 重定位。

    裁定:

    1. 基线 rc.3;stale-premise 复核 src/apps/crm.app.ts:130-140 Service 分组三项、Tasks 的真实分组归属(:84/:93)、导航 label「Service Overview」。
    2. 四项对齐真实导航:Service Board 不存在(真名 case_workflow/Service Workflow,且不是导航项——沿 docs(service): write the sla page's views, report dimensions and business-hours claims to source (#917) #924 已立口径)、Tasks 写实其真实分组、补真实存在的 Knowledge、label 写实。
    3. docs(service): 把 service/index 的升级与通知五条说法按 flow / hook 写实(#904) #913/docs(service): cases 升级整节与 index 生命周期第 2 步按 flow / hook 写实(#914、#915) #922 已落地行零回退(:27/:30/:36/:37/:38/:40/:48);SLA policy matrix: per-priority × tier clocks, first-response stamping, escalation that reassigns #595/Case intake: round-robin assignment + triage view so web-to-case never lands ownerless #596 不预判;src/ 零改动;三语同步;zh 内链不带锚。

    Generated by Claude Code

  4. yinlianghui
    closed this as completedin #932on Aug 6, 2026

  5. yinlianghui commented on Aug 6, 2026

    @yinlianghui
    yinlianghui
    on Aug 6, 2026 – with Claude
    CollaboratorAuthor

    ✅ 验收通过 —— PR #932 已转 ready 并挂 auto-merge(CI 8/8 全绿实核)。

    验收要点:

    1. 四项前提逐条成立(行号重定位 :63-67→:60-67 如实记录);group_service 实有且仅有三项(Cases/Knowledge/Service Overview)以 crm.app.ts 行号为证。
    2. 改法沿 docs(service): write the sla page's views, report dimensions and business-hours claims to source (#917) #924 口径:三项写实 + Tasks/Service Board 两个读者会带着来的名字给真实归属(My Work 分组 / Service Workflow 页签),不静默删名;SLA policy matrix: per-priority × tier clocks, first-response stamping, escalation that reassigns #595/Case intake: round-robin assignment + triage view so web-to-case never lands ownerless #596 不预判。
    3. 面控:三份 diff 仅两个 hunk(@@ -62 / @@ -64,4),docs(service): 把 service/index 的升级与通知五条说法按 flow / hook 写实(#904) #913/docs(service): cases 升级整节与 index 生命周期第 2 步按 flow / hook 写实(#914、#915) #922 已落地行零回退;与 service/cases 的「标准列表视图」七个名字里有六个不存在（:114-121），经理提示的三条（Breached SLA / Service Board / 客服排行榜）同族 #926 的 cases 页 Service Board 归属正确切割。
    4. 守卫盲区如实报(无检查读导航散文,predicted GREEN 且注明测试不构成正确性证据)。

    越界发现处置(两单已复核成立,标 pm:queue):

    断流记录:本单报告 10:26Z 写完但任务未关(#901 型),PM 于 12:34Z 从 transcript 回收报告验收,无工作损失。

    Generated by Claude Code

  6. yinlianghui
    added 4 commits that reference this issue on Aug 10, 2026

    docs(service): write the index page's "Where to find things" list to …

    834870c

    docs(marketing): name Products in the index page's "Where to find thi…

    2a03ca2

    docs(service): write the index page's dashboards & reports section to…

    9cd96f6

    docs(getting-started): write the quick tour's navigation table to the…

    02fb379
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationpm:dispatchedDispatched to a dev agent by /pm-dispatch

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions