跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

jira-lifecycle-management

Manage issue lifecycle through workflow transitions and status changes. Control who does what and when via assignments, versions, and components.

jira-assistant-skills · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add grandcamel/JIRA-Assistant-Skills --skill jira-lifecycle-management

技能说明


name: "jira-lifecycle-management" description: "Manage issue lifecycle through workflow transitions and status changes. Control who does what and when via assignments, versions, and components." version: "1.0.0" author: "jira-assistant-skills" license: "MIT" allowed-tools: ["Bash", "Read", "Glob", "Grep"]

jira-lifecycle

Workflow and lifecycle management for JIRA issues.

Risk Levels

OperationRiskNotes
List transitions-Read-only
List versions/components-Read-only
Transition issue!Can transition back
Assign/unassign!Can reassign
Resolve issue!Can reopen
Reopen issue!Can resolve again
Create version/component-Easily reversible
Update version/component!Can be undone
Release version!Can unrelease
Archive version!Can unarchive
Delete component!!Issues lose component association

Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible

Quick Discovery

Use this skill to: Drive issues through workflows, assign ownership, manage releases and components.

Not for: Creating/editing issue content (use jira-issue) or finding issues (use jira-search).

Also see: Workflow Guide | JSM Workflows | Best Practices

What this skill does

IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.

7 command categories for complete lifecycle management:

CategoryPurposeExample
TransitionsMove issues between statusesjira-as lifecycle transition PROJ-123 --to "In Progress"
AssignmentsControl ownershipjira-as lifecycle assign PROJ-123 --self or --user email
ResolutionMark issues completejira-as lifecycle resolve PROJ-123 --resolution Fixed
ReopenRestore resolved issuesjira-as lifecycle reopen PROJ-123
VersionsPlan and track releasesjira-as lifecycle version create PROJ --name "v2.0.0"
ComponentsOrganize by subsystemjira-as lifecycle component create PROJ --name "API"
DiscoveryView available optionsjira-as lifecycle transitions PROJ-123

All commands support --help for full option documentation.

Available Commands

Workflow Transitions

jira-as lifecycle transitions PROJ-123                    # List available transitions
jira-as lifecycle transitions PROJ-123 --output json      # Output as JSON
jira-as lifecycle transition PROJ-123 --to "In Progress"  # Transition by status name
jira-as lifecycle transition PROJ-123 --id 31             # Transition by ID
jira-as lifecycle transition PROJ-123 --to Done --resolution Fixed  # With resolution
jira-as lifecycle transition PROJ-123 --to "In Progress" --comment "Starting work"  # With comment
jira-as lifecycle transition PROJ-123 --to "In Progress" --sprint 42  # Move to sprint after transition
jira-as lifecycle transition PROJ-123 --to Done --dry-run             # Preview without executing
jira-as lifecycle transition PROJ-123 --to Done --fields '{"customfield_10001": "value"}'  # With custom fields

Tip: jira-as issue transition and jira-as issue transitions are aliases for these two commands, with the same options (see the jira-issue skill).

Assignments

jira-as lifecycle assign PROJ-123 --self                  # Assign to yourself
jira-as lifecycle assign PROJ-123 --user email@example.com  # Assign to user
jira-as lifecycle assign PROJ-123 --unassign              # Remove assignee

Resolution

jira-as lifecycle resolve PROJ-123                         # Resolve issue (may require --resolution)
jira-as lifecycle resolve PROJ-123 --resolution Fixed      # Resolve with specific resolution
jira-as lifecycle resolve PROJ-123 --resolution Fixed --comment "Fixed in v1.2.0"  # With comment
jira-as lifecycle reopen PROJ-123                          # Reopen issue
jira-as lifecycle reopen PROJ-123 --comment "Reopening for additional work"  # Reopen with comment

Version Management

jira-as lifecycle version list PROJ                       # List versions
jira-as lifecycle version list PROJ --output json         # Output as JSON
jira-as lifecycle version list PROJ --unreleased          # Show only unreleased versions
jira-as lifecycle version list PROJ --archived            # Include archived versions
jira-as lifecycle version create PROJ --name "v2.0.0"     # Create version
jira-as lifecycle version create PROJ --name "v2.0.0" --description "Major release"  # With description
jira-as lifecycle version create PROJ --name "v2.0.0" --start-date 2026-01-01 --release-date 2026-03-01
jira-as lifecycle version create PROJ --name "v2.0.0" --released --dry-run  # Preview creation
jira-as lifecycle version create PROJ --name "v2.0.0" --archived  # Create as archived
jira-as lifecycle version release PROJ "v1.0.0"           # Release a version
jira-as lifecycle version release PROJ "v1.0.0" --move-unfixed "v1.1.0"  # Move unfixed issues to another version
jira-as lifecycle version archive PROJ "v0.9.0"           # Archive a version

Component Management

Note: Component update and delete operations require the component ID (not name). Use jira-as lifecycle component list PROJ to find component IDs. The --lead option requires an account ID, not email.

jira-as lifecycle component list PROJ                     # List components (shows IDs)
jira-as lifecycle component list PROJ --output json       # Output as JSON
jira-as lifecycle component create PROJ --name "API"      # Create component
jira-as lifecycle component create PROJ --name "API" --description "REST API layer"  # With description
jira-as lifecycle component create PROJ --name "Backend" --lead
阅读完整来源 ↗