rhdh-jira-sprint-report

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Report on an RHDH sprint

RHDH冲刺报告

Say what the sprint actually delivered, with the numbers traceable to a query. Read-only.

说明冲刺实际交付的内容，所有数据均可追溯至查询结果。只读权限。

Route

使用路径

Load

workflows/summarize-sprint.md

. Run it at the end of a sprint, before the review and demo meeting.

加载

workflows/summarize-sprint.md

。在冲刺结束时、评审和演示会议之前运行。

Boundary with the neighbouring skills

与相邻技能的边界

Preparing the sprint that has not started — carryover, capacity, ready queue — is
```
/rhdh-jira-sprint-plan
```
. This skill looks back; that one looks forward.
Judging whether individual issues are in good shape is
```
/rhdh-jira-refine
```
.
Board IDs, sprint naming, JQL, and custom field IDs are
```
/rhdh-jira-api
```
.
Release-level readiness across sprints is
```
/rhdh-release-status
```
.

筹备尚未启动的冲刺（包括工作结转、团队产能、就绪队列）属于
```
/rhdh-jira-sprint-plan
```
技能。本技能用于回顾已完成工作，而该技能用于规划未来工作。
判断单个问题状态是否良好属于
```
/rhdh-jira-refine
```
技能。
看板ID、冲刺命名、JQL和自定义字段ID相关内容属于
```
/rhdh-jira-api
```
技能。
跨冲刺的发布级就绪状态属于
```
/rhdh-release-status
```
技能。

Completion

完成标准

Complete when committed and completed totals name the sprint and the JQL behind them, the partition into completed, carried over, and added mid-sprint accounts for every issue in the sprint, and epic progress states both the numerator and the denominator. Report whether any search was truncated. The per-member breakdown says out loud that it covers only Jira-tracked work — code review, documentation, support, and meetings do not appear in it, and someone with zero completions has not necessarily done nothing.

当报告中明确标注冲刺名称及背后的JQL查询语句，且对冲刺中的所有问题按已完成、结转、中期新增进行划分，同时史诗进度明确标注分子和分母时，即完成报告。需说明是否有搜索结果被截断。按成员划分的工作明细需明确说明，仅涵盖Jira追踪的工作——代码评审、文档编写、支持工作和会议内容未纳入其中，完成数为零的成员未必没有开展工作。