From 546131e360a3450e54c9d9087b8759237eb323de Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 6 Aug 2026 14:59:29 +0000 Subject: [PATCH] docs(sales): name the real dashboard and report in the forecasting roll-up (#985) The "Forecasting roll-up" list on content/docs/sales/pipeline-management.mdx pointed at a "Sales Dashboard" and a "Pipeline Coverage" report holding a "quarter x stage" matrix. Neither was findable as written. sales_dashboard renders under the label "Sales Performance", which is also its Sales sidebar entry (src/dashboards/sales.dashboard.ts:22, src/apps/crm.app.ts:61). And pipeline_coverage_by_quarter is a matrix over forecast_category (rows) by close_quarter (columns) with total_amount and opp_count in each cell; stage appears only in the runtimeFilter that drops closed deals, so it is not an axis at all (src/reports/opportunity.report.ts:35-42). Both lines now carry the real label plus the metadata identifier, in all three locales, worded the same way as the entry PR #975 landed on analytics/reports so the two pages no longer contradict each other. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01VHrPAGEgFDoHjphqYG4BMa --- ...e-management-forecast-rollup-real-names.md | 25 +++++++++++++++++++ content/docs/sales/pipeline-management.mdx | 4 +-- .../sales/pipeline-management.zh-Hans.mdx | 4 +-- .../sales/pipeline-management.zh-Hant.mdx | 4 +-- 4 files changed, 31 insertions(+), 6 deletions(-) create mode 100644 .changeset/pipeline-management-forecast-rollup-real-names.md diff --git a/.changeset/pipeline-management-forecast-rollup-real-names.md b/.changeset/pipeline-management-forecast-rollup-real-names.md new file mode 100644 index 00000000..a74ac410 --- /dev/null +++ b/.changeset/pipeline-management-forecast-rollup-real-names.md @@ -0,0 +1,25 @@ +--- +'hotcrm': patch +--- + +Name the dashboard and the report that the sales pipeline page's "Forecasting +roll-up" list actually points at. + +`content/docs/sales/pipeline-management.mdx` told a sales manager the forecast +view is built from a **Sales Dashboard** and a **Pipeline Coverage** report +holding a *quarter × stage* matrix. Neither was findable as written. There is no +dashboard called *Sales Dashboard*: the identifier is `sales_dashboard`, but the +label it renders under — and the label on its Sales sidebar entry — is **Sales +Performance**. And the Pipeline Coverage report's matrix has neither of the axes +the page named: `pipeline_coverage_by_quarter` puts **forecast category** down +the rows and **close quarter** across the columns, with amount and deal count in +each cell; `stage` appears only in the runtime filter that drops closed deals, so +it is not an axis at all. A reader who took the page at its word was reading the +matrix transposed and against the wrong dimension. + +Both lines now carry the real label plus the metadata identifier behind it, in +all three locales, and the report line is worded the same way as the entry on +the reports page so the two pages no longer contradict each other. The Pipeline +Coverage line also states the report's own label, **Pipeline Coverage by +Forecast × Quarter**, which is how the report library lists it — the sidebar +shows the shorter **Pipeline Coverage**. diff --git a/content/docs/sales/pipeline-management.mdx b/content/docs/sales/pipeline-management.mdx index d623dfeb..2d614989 100644 --- a/content/docs/sales/pipeline-management.mdx +++ b/content/docs/sales/pipeline-management.mdx @@ -91,8 +91,8 @@ See [Analytics › Reports](/docs/analytics/reports) for details. The Sales Manager / Director view of the forecast is built from: - The **Opportunity Metrics** dataset (`opportunity_metrics`) — measure **Total Amount** (sum of amount), dimension **Stage** -- The **Sales Dashboard** widgets (pipeline by stage, win rate, top deals) -- The **Pipeline Coverage** report (quarter × stage matrix) +- The **Sales Performance** dashboard (`sales_dashboard`) — widgets for pipeline by stage, win rate, top deals +- The **Pipeline Coverage** report (`pipeline_coverage_by_quarter`, whose own label reads **Pipeline Coverage by Forecast × Quarter**) — a matrix of open pipeline: forecast category down the rows, close quarter across the columns Together they answer: *"do we have enough pipeline to make the quarter, and where are the risks?"* diff --git a/content/docs/sales/pipeline-management.zh-Hans.mdx b/content/docs/sales/pipeline-management.zh-Hans.mdx index 1fd88a2a..cc457ed6 100644 --- a/content/docs/sales/pipeline-management.zh-Hans.mdx +++ b/content/docs/sales/pipeline-management.zh-Hans.mdx @@ -91,8 +91,8 @@ description: 销售管道的日常运作方式——推进交易、自动概率 销售经理 / 总监的预测视图由以下部分构建： - **Opportunity Metrics** dataset（`opportunity_metrics`）—— 度量 **Total Amount**（金额之和），维度 **Stage** -- **销售仪表盘**小部件（按阶段的销售管道、赢单率、顶级交易） -- **销售管道覆盖率**报告（季度 × 阶段矩阵） +- **Sales Performance** 仪表盘（`sales_dashboard`）—— 小部件包括按阶段的销售管道、赢单率、顶级交易 +- **Pipeline Coverage** 报告（`pipeline_coverage_by_quarter`，报表自身的 label 写作 **Pipeline Coverage by Forecast × Quarter**）—— 未结管道的矩阵：行是预测类别，列是预计成交季度 它们共同回答：*"我们是否有足够的销售管道来完成本季度，以及风险在哪里？"* diff --git a/content/docs/sales/pipeline-management.zh-Hant.mdx b/content/docs/sales/pipeline-management.zh-Hant.mdx index 788c732d..eaef1e13 100644 --- a/content/docs/sales/pipeline-management.zh-Hant.mdx +++ b/content/docs/sales/pipeline-management.zh-Hant.mdx @@ -91,8 +91,8 @@ description: 銷售管道的日常運作方式——推進交易、自動機率 銷售經理 / 總監的預測視圖由以下部分構建： - **Opportunity Metrics** dataset（`opportunity_metrics`）—— 度量 **Total Amount**（金額之和），維度 **Stage** -- **銷售儀表板**小工具（按階段的銷售管道、贏單率、頂級交易） -- **銷售管道覆蓋率**報告（季度 × 階段矩陣） +- **Sales Performance** 儀表板（`sales_dashboard`）—— 小工具包括按階段的銷售管道、贏單率、頂級交易 +- **Pipeline Coverage** 報告（`pipeline_coverage_by_quarter`，報表自身的 label 寫作 **Pipeline Coverage by Forecast × Quarter**）—— 未結管道的矩陣：列是預測類別，欄是預計成交季度 它們共同回答：*"我們是否有足夠的銷售管道來完成本季度，以及風險在哪裡？"*