jira-lifecycle_skill

Overview

This skill manages JIRA issue lifecycles by driving workflow transitions, controlling assignments, and managing versions and components. It exposes commands to transition, resolve, reopen, assign, and operate on release/version and component metadata. Use the provided CLI to preview changes, run dry-runs, and format output as text or JSON. Built for automation and safe day-to-day operations with clear risk levels for each action.

How this skill works

Operate via the jira-as lifecycle CLI to inspect available transitions, perform status changes, and manage ownership, versions, and components. Most modify actions support --dry-run to preview changes before applying them. Discovery commands list transitions, versions, and components (with IDs) so you can script reliable transitions and component updates. Follow environment variable configuration for credentials (JIRA_SITE_URL, JIRA_EMAIL, JIRA_API_TOKEN).

When to use it

• Move issues through a workflow step (e.g., start work, mark QA, mark done).
• Assign or reassign work to team members or remove assignees.
• Resolve or reopen issues as part of release or bug triage.
• Create, release, archive, or list versions when planning releases.
• Create, update, or delete components while organizing project subsystems.
• Preview changes with --dry-run before executing risky operations.

Best practices

• Always run discovery (transitions/versions/components) before making changes to confirm IDs and available actions.
• Use --dry-run to validate effects and required fields for transitions that need custom fields or resolutions.
• Prefer transitioning by explicit ID or exact status name to avoid ambiguity in customized workflows.
• Be cautious with destructive operations (component delete) — use --move-to to preserve associations.
• Give clear comments and resolutions when resolving or reopening to keep audit trails.

Example use cases

• Transition PROJ-123 to 'In Progress' and add a work comment while moving the issue into a sprint.
• Assign a set of issues to the current user during daily standup scripting with --self and --dry-run to validate.
• Create a new release version v2.0.0 with start and release dates, previewing with --dry-run.
• Archive an old version after release and move any unfixed issues to a maintenance version.
• List components to find a component ID, then safely update its lead or description using the ID.