ReddRadar
Agent skill
ticket-transition
Change a Jira ticket's workflow status. Use when the user wants to move a ticket to a different status, start work, complete a task, or change workflow state.
Install this agent skill to your Project
npx add-skill https://github.com/rlcurrall/aide/tree/main/skills/ticket-transition
SKILL.md
Transition Ticket Status
Change the workflow status of a Jira ticket (e.g., move to "In Progress", "Done").
When to Use
- User wants to start work on a ticket
- User has completed work and wants to close a ticket
- User wants to move a ticket to a different status
- User needs to see available status transitions
How to Execute
List available transitions first:
aide jira transition TICKET-KEY --list
Then transition to desired status:
aide jira transition TICKET-KEY "Status Name" [options]
Flags
| Flag | Short | Description |
|---|---|---|
--list |
-l |
List available transitions for the ticket |
--comment |
-c |
Add comment with the transition |
--resolution |
-r |
Set resolution (for Done/Resolved transitions) |
--format |
Output format: text, json, markdown |
Output
When transitioning:
- Confirmation of successful transition
- New status name
- URL to view the ticket
When listing (--list):
- Available transition names
- Target status for each transition
Common Patterns
# List available transitions
aide jira transition PROJ-123 --list
# Move ticket to In Progress
aide jira transition PROJ-123 "In Progress"
# Complete a ticket with comment
aide jira transition PROJ-123 "Done" --comment "Implementation complete, tests passing"
# Resolve with specific resolution
aide jira transition PROJ-123 "Done" --resolution "Fixed"
# Move to code review
aide jira transition PROJ-123 "Code Review"
Common Status Names
Status names vary by project workflow. Common ones include:
| Category | Status Names |
|---|---|
| Not Started | To Do, Open, Backlog |
| In Progress | In Progress, In Development |
| Review | Code Review, In Review, QA |
| Completed | Done, Closed, Resolved |
Best Practices
- Always list available transitions first with
--list - Add comments when transitioning to explain the change
- Set resolution when closing tickets
- Check workflow requirements - some transitions need fields set
Workflow Example
# 1. Start work
aide jira transition PROJ-123 "In Progress" --comment "Starting implementation"
# 2. Move to review
aide jira transition PROJ-123 "Code Review" --comment "PR #456 ready for review"
# 3. Complete work
aide jira transition PROJ-123 "Done" --comment "Merged and deployed" --resolution "Fixed"
Next Steps
After transitioning:
- Use ticket skill to verify the new status
- Use ticket-comment skill to add additional notes
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
rlcurrall/aide
release
Create a new software release by bumping version numbers, committing changes, creating git tags, and pushing to remote. Use when creating a release, bumping versions, or publishing a new version.
rlcurrall/aide
ticket-attach
Manage Jira ticket attachments. Use when the user wants to list, upload, download, or delete attachments on a ticket.
rlcurrall/aide
pr-comments
Load PR comments and feedback for code review. Use when the user wants to see reviewer feedback, check for unresolved comments, understand what changes are requested, or review discussion on a PR.
rlcurrall/aide
pr-list
List pull requests from the repository. Use when the user wants to see open PRs, find PRs to review, check their own PRs, or browse PR history.
rlcurrall/aide
ticket-update
Update fields on an existing Jira ticket. Use when the user wants to modify a ticket's summary, description, assignee, priority, labels, or custom fields.
rlcurrall/aide
pr-create
Create a new pull request. Use when the user wants to open a PR, submit code for review, create a draft PR, or push changes for merge.
Didn't find tool you were looking for?