45 lines
1.8 KiB
Markdown
45 lines
1.8 KiB
Markdown
---
|
||
title: "Jira Gate"
|
||
type: concept
|
||
tags: ["project-management", "jira", "workflow", "quality-gate"]
|
||
last_updated: 2026-04-25
|
||
---
|
||
|
||
## Definition
|
||
|
||
Jira Gate（Jira 门控）是 [[Jira Workflow Steward]] Agent 实施的一项强制性工作流规则：**在没有有效 Jira Task ID 的前提下，不生成任何分支名、提交信息或 Git 工作流建议**。Jira Task ID 是所有交付输出的前提条件。
|
||
|
||
## Rules
|
||
|
||
1. **Never generate without Jira ID**：分支名、commit message、PR 标题均必须包含有效 Jira Task ID
|
||
2. **Exact preservation**：严格使用 Jira ID 原样，不得发明、规范或猜测缺失的 ticket 引用
|
||
3. **Prompt for ID, don't guess**：若 Jira 任务缺失，则请求补充，而非自动创建 ID
|
||
|
||
> 若 Jira 任务缺失，询问：`Please provide the Jira task ID associated with this work (e.g. JIRA-123).`
|
||
|
||
## External Prefix Handling
|
||
|
||
若外部系统（如 AI 编码 agent）添加了外层前缀，分支名内部仍需保持仓库原生格式：
|
||
|
||
- ✅ `codex/feature/JIRA-214-add-sso-login`（仓库格式在外部包装内保持不变）
|
||
- ❌ `feature/JIRA-214-add-sso-login` → `codex/JIRA-214-add-sso-login`（丢失仓库类型信息）
|
||
|
||
## Gate Position in Workflow
|
||
|
||
```
|
||
[Request] → [Jira Gate: 要求 Jira ID] → [Branch Strategy] → [Atomic Commits] → [PR Template] → [Release]
|
||
↓
|
||
[无 Jira ID → 停止并请求]
|
||
```
|
||
|
||
Jira Gate 位于整个交付链路的最前端，是第一道质量门。
|
||
|
||
## Relationship to Other Concepts
|
||
|
||
- [[Jira-Git-Traceability]]：Jira Gate 是 Jira-Git Traceability 的第一步门控
|
||
- [[Branch-Strategy]]：Gate 通过后才进入分支策略流程
|
||
- [[Pull-Request-Governance]]：PR 合并同样需要 Jira ID 验证
|
||
|
||
## Sources
|
||
- [[project-management-jira-workflow-steward]]
|