rhdh-jira-create

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Create RHDH Jira work

创建RHDH Jira工单

One skill for "this should be a ticket". It decides the issue type and project, runs the interview, drafts from the RHDH template, and creates the issue.

A caller who says "file this in Jira" almost never knows whether they want a Feature, an Epic, or a Story. Deciding that is this skill's job. Getting it wrong writes the wrong issue type into a public project, so the decision happens up front and out loud, and the user confirms it before anything is created.

这是一款用于处理“此事应创建工单”需求的技能。它会判定工单类型和所属项目，执行问询流程，基于RHDH模板草拟工单并完成创建。

当调用者说“在Jira中提交此事”时，他们几乎不清楚自己需要的是Feature、Epic还是Story。这类判定工作由本技能负责。若判定错误，会将错误的工单类型写入公开项目，因此判定流程会提前明确告知用户，并在创建任何内容前获得用户确认。

Route

流程路径

Load

workflows/create-issue.md

. One workflow covers every level of the hierarchy — the type decision is its first real step, and the steps after it converge.

Add

references/support-intake.md

when the work originates from a support case: an RHDHSUPP conversation, a customer escalation, an SLA question, or a request to turn a case into a defect or a feature request.

加载

workflows/create-issue.md

。一个工作流可覆盖所有层级的工单——类型判定是首个核心步骤，后续步骤会逐步收敛。

当工单源自支持案例时，需添加

references/support-intake.md

：包括RHDHSUPP对话、客户升级请求、SLA相关问题，或是将案例转换为缺陷工单或需求工单的请求。

Grilling is a hard gate

Grilling是硬性前置要求

Creation requires the external

grilling

skill. It is not bundled with this pack. If the host cannot invoke it by name, stop before creating anything, say that creation is gated on

grilling

, and name

/setup-rhdh-skills install

. Never probe host skill directories, install it yourself, or improvise a substitute interview.

/rhdh-jira-authoring

carries the RHDH half of the interview — the challenge matrix, field inference, sizing, and templates. Invoke it by name.

创建工单需要调用外部

grilling

技能，该技能未包含在当前包内。若主机无法通过名称调用它，则需在创建任何内容前停止操作，告知用户创建工单需以

grilling

为前置条件，并提示使用

/setup-rhdh-skills install

进行安装。切勿探查主机技能目录、自行安装或临时替代问询流程。

/rhdh-jira-authoring

负责RHDH侧的问询流程——包括挑战矩阵、字段推断、规模评估和模板调用。需通过名称调用该技能。

Every create is an external write

所有创建操作均为外部写入

Invoke

/mutation-gate

and follow it before any

acli

command that creates, links, comments, or edits. One create is rarely one operation — the create, the field update

create

could not carry, the parent link, and the comment go into the same stated set so a single approval covers them.

Afterwards, read the issue back. A create that succeeded followed by a field update that silently failed is a half-created issue, not a success.

在执行任何用于创建、关联、评论或编辑的

acli

命令前，需先调用

/mutation-gate

并遵循其要求。一次创建操作通常涉及多个步骤——创建工单、补充设置

create

命令无法携带的字段、添加父链接和评论，这些操作需纳入同一审批集合，只需一次审批即可覆盖所有步骤。

操作完成后，需回读工单信息。若创建成功但字段更新静默失败，则视为工单未完全创建，不判定为操作成功。

Boundary with the neighbouring skills

与相邻技能的边界划分

Judging whether an existing issue is ready is
```
/rhdh-jira-refine
```
.
Changing status, assignee, comments, or links on a known key is
```
/rhdh-jira-update
```
.
```
acli
```
syntax, field IDs, the component catalog, and workflow exit criteria are
```
/rhdh-jira-api
```
.
Templates, the challenge matrix, sizing, duplicate detection, and decomposition rules are
```
/rhdh-jira-authoring
```
.
Creating a PR and linking it back to an issue is
```
/rhdh-jira-link
```
.

判断现有工单是否就绪：
```
/rhdh-jira-refine
```
修改已知工单的状态、经办人、评论或链接：
```
/rhdh-jira-update
```
```
acli
```
语法、字段ID、组件目录和工作流退出标准：
```
/rhdh-jira-api
```
模板、挑战矩阵、规模评估、重复检测和拆分规则：
```
/rhdh-jira-authoring
```
创建PR并关联至工单：
```
/rhdh-jira-link
```

Completion

完成标准

Complete when the user confirmed the issue type before creation, the duplicate check ran and its result was reported, the grilling interview happened, and every created key has been read back and reported with its resulting status, parent link, and the fields that were actually set. Report any field the API refused as unset, never as set. A decomposition is complete only when the user approved the batch table before any child was created, and every child in that table has either a key or a stated reason it was skipped.

满足以下条件时判定操作完成：用户在创建前确认了工单类型、完成重复检测并上报结果、执行了grilling问询流程、所有已创建工单的编号均已回读，并上报其最终状态、父链接及实际设置的字段。对于API拒绝设置的字段，需上报为未设置，而非已设置。拆分操作的完成标准为：用户在创建子工单前已批准批量表格，且表格中的每个子工单要么已生成编号，要么已说明跳过原因。