Back to Details

044-planning-jira

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Jira CLI - issues, workflows, and discussion for analysis

Jira CLI - 用于分析的问题、工作流及讨论内容

Use 
jira
 to work with Jira issues: first run an interactive check - if 
jira
is not installed, stop, ask whether the user wants installation guidance, wait for an answer, then continue. When 
jira
is available, validate configuration, list issues with optional JQL filters, render markdown tables from command output, and load full issue descriptions and comment threads for analysis.
What is covered in this Skill?
  • Interactive install gate: ask before assuming 
    jira
    is installed; offer installation guidance only when the user agrees
  • Install/config checks (
    jira version
    , 
    jira configure
    )
  • Jira Cloud context (site URL, account email, API token handled by CLI prompts)
  • Issue lists: basic list and JQL-backed list queries
  • Deep reads: issue detail and comments for requirement analysis
  • Core actions: create, assign, transition, and add comments
使用**
jira
处理Jira问题：首先执行交互式检查——如果未安装
jira
，请暂停**，询问用户是否需要安装指南，等待用户回复后再继续。当
jira
可用时，验证配置信息，通过可选的JQL过滤器列出问题，将命令输出渲染为Markdown表格，并加载完整的问题描述和评论线程用于分析。
本技能涵盖哪些内容？
  • 交互式安装校验：在假设
    jira
    已安装前先询问用户；仅在用户同意时提供安装指南
  • 安装/配置检查（
    jira version
    、
    jira configure
    ）
  • Jira Cloud环境配置（站点URL、账户邮箱、API令牌由CLI提示处理）
  • 问题列表：基础列表查询和基于JQL的列表查询
  • 深度读取：用于需求分析的问题详情和评论
  • 核心操作：创建、分配、流转问题以及添加评论

Constraints

约束条件

Do not fabricate issue data; use only 
jira
output (or explicitly agreed Jira REST API responses). Never print API tokens or secrets.
  • INTERACTIVE GATE: If 
    jira
    is missing, stop, ask whether the user wants installation guidance, wait - do not skip to issue listing
  • FIRST (after gate): Verify 
    jira
    is available before issuing subcommands
  • CONFIG: Ensure Jira CLI is configured before private workspace operations
  • TABLES: Prefer markdown pipe tables for issue list summaries
  • THREAD: For analysis, include description and all comments (or explicitly summarize with omissions noted)
请勿编造问题数据；仅使用
jira
的输出（或明确约定的Jira REST API响应）。切勿打印API令牌或机密信息。
  • 交互式校验机制：如果未找到
    jira
    ，请暂停，询问用户是否需要安装指南，等待用户回复——不要直接跳转到问题列表
  • 第一步（校验之后）：在执行子命令前先验证
    jira
    是否可用
  • 配置：在进行私有工作区操作前确保Jira CLI已完成配置
  • 表格：优先使用Markdown管道表格展示问题列表摘要
  • 线程：用于分析时，需包含问题描述和所有评论（或明确说明省略部分的摘要）

When to use this skill

何时使用本技能

  • jira issue list
  • List Jira issues
  • Jira JQL issue query
  • jira issue view comments
  • Jira CLI issue workflow
  • jira issue list
  • 列出Jira问题
  • Jira JQL问题查询
  • jira issue view comments
  • Jira CLI问题工作流

Reference

参考资料

For detailed guidance, examples, and constraints, see references/044-planning-jira.md.
如需详细指南、示例和约束条件，请查看references/044-planning-jira.md。