jira
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseJira Ticket
Jira工单
Generate a structured Jira ticket description from context (conversation, code changes,
PR, or user description).
根据上下文(对话、代码变更、PR或用户描述)生成结构化的Jira工单描述。
Output Format
输出格式
text
**Title:** <imperative mood, concise>
**Type:** <Task | Bug | Story | Spike | Sub-task>
**Priority:** <Critical | High | Medium | Low>
**Component:** <infer from context, e.g. CI/CD, Auth, Tests, UI>
**Description:**
<1-2 sentences explaining the what and why>
**Acceptance Criteria:**
- <testable criterion>
- <testable criterion>
- ...
**PR:** <link if one exists>text
**标题:** <祈使语气,简洁明了>
**类型:** <任务 | 缺陷 | 用户故事 | 研究任务 | 子任务>
**优先级:** <紧急 | 高 | 中 | 低>
**组件:** <从上下文推断,例如CI/CD、认证、测试、UI>
**描述:**
<1-2句话说明内容和原因>
**验收标准:**
- <可测试的标准>
- <可测试的标准>
- ...
**PR:** <如有链接则填写>Rules
规则
- Title: imperative mood, no Jira prefix (the user adds their own project key)
- Description: concise — explain the problem and the solution direction, not implementation details
- Acceptance criteria: specific, testable, checkboxable — not vague ("works correctly")
- Priority: infer from context (security = High/Critical, cosmetic = Low, functional = Medium)
- Component: infer from files touched or domain discussed
- PR link: include if a PR was created in the same conversation
- Omit optional fields (Epic, Sprint, Story Points) unless the user asks for them
- 标题:使用祈使语气,不要添加Jira前缀(用户会自行添加项目键)
- 描述:简洁明了——说明问题和解决方向,而非实现细节
- 验收标准:具体、可测试、可勾选——避免模糊表述(如“正常工作”)
- 优先级:从上下文推断(安全问题=高/紧急,外观问题=低,功能问题=中)
- 组件:根据涉及的文件或讨论的领域推断
- PR链接:如果对话中已创建PR则包含
- 省略可选字段(史诗、迭代、故事点数),除非用户要求添加
Examples
示例
Good acceptance criteria:
- assigns the PR author on
pr-auto-assign.ymleventsopened - is deleted
bin/assign-random-codeowner.sh - CODEOWNERS review requests are unaffected
Bad acceptance criteria:
- It works
- The workflow is correct
- Tests pass
良好的验收标准:
- 在
pr-auto-assign.yml事件中自动分配PR作者opened - 被删除
bin/assign-random-codeowner.sh - CODEOWNERS的审核请求不受影响
糟糕的验收标准:
- 它能正常工作
- 工作流正确
- 测试通过