auto-update-jira-status

Automates Jira Cloud ticket status transitions via URL and issue key.

2|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/Tasup/Tasup --skill auto-update-jira-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-update-jira-status
Source: https://github.com/Tasup/Tasup/tree/main/.claude/skills/auto-update-jira-issue-status
Command: npx skills add https://github.com/Tasup/Tasup --skill auto-update-jira-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually updating Jira ticket statuses is repetitive and time-consuming, especially when managing multiple tickets or coordinating with development workflows. This skill automates that process, ensuring your project board is always current.

Core Features & Use Cases

  • Automatic Status Progression: Seamlessly moves Jira tickets through common workflow stages (e.g., TODO → In Progress → Done).
  • Smart Workflow Integration: Adapts to Jira's specific workflow transitions, ensuring valid status changes.
  • Use Case: When you create a new development branch for a Jira ticket, this skill can automatically mark the ticket as "In Progress," keeping your project board always up-to-date without manual intervention.

Quick Start

Update Jira ticket https://yourcompany.atlassian.net/browse/PROJ-123 to its next logical status.

Frequently Asked Questions about auto-update-jira-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Jira ticket status updates in my workflow?

Automate Jira status updates by providing a ticket URL; the skill automatically detects the next workflow stage and transitions the issue, or prompts you to select from available transitions if the next step is ambiguous.

Can I use this to update Jira Cloud issues automatically?

Yes, this skill works with Jira Cloud issues accessed via URLs. It extracts the site URL and issue key, retrieves available transitions for that ticket, and executes the appropriate status change based on your workflow.

What happens if my Jira workflow has custom or non-standard status names?

The skill handles multilingual and custom status names by retrieving the available transitions for your specific issue and matching against common workflow mappings; if no automatic match exists, it prompts you to manually select the correct transition.

How does the skill know which status to transition to next?

The skill determines the next status by mapping common workflow progressions like TODO → In Progress → Done, then validates against your Jira instance's actual available transitions and executes the matching one.

What if a status transition isn't available for my ticket?

If automatic flow is unavailable, the skill displays all valid transitions for that issue and prompts you to manually select which one to execute, then verifies the update completed successfully.

Does this work with multiple Jira projects and different workflow configurations?

Yes, the skill adapts to each Jira instance's specific workflow by retrieving current issue data and available transitions dynamically, so it works across projects and custom workflow configurations.