| name | ticket |
| description | View Jira ticket details to understand requirements and context. Use when the user mentions a ticket key, wants to understand a task, needs to load ticket context, or starts work on an issue. |
| allowed-tools | Bash(aide:*) |
View Jira Ticket
Fetch detailed information about a Jira ticket to understand requirements and context.
When to Use
- User mentions a ticket key (e.g., "PROJ-123")
- User wants to understand a task's requirements
- User asks "what's this ticket about?"
- User is starting work on an issue
How to Execute
Run:
aide jira view <TICKET-KEY> [--format text|json|markdown]
Output Includes
- Summary and description
- Status, priority, type
- Assignee and reporter
- Labels and components
- Created and updated dates
- Any linked issues
Ticket-Driven Development Workflow
Starting Work on a Ticket
- Load ticket context: Use this skill to fetch full details
- Understand requirements: Review description and acceptance criteria
- Check for blockers: Look for linked issues or dependencies
- Review comments: Use ticket-comments skill for discussion history
During Development
- Reference ticket requirements while coding
- Track progress with comments using ticket-comment skill
- Update description if scope changes using ticket-update skill
- Stay aligned by checking for new comments
Completing Work
- Add summary comment documenting what was implemented
- Reference in commits (e.g., "PROJ-123: Add feature")
- Link PR in closing comment
- Transition status using ticket-transition skill
Best Practices
- Always load ticket context before starting implementation
- Keep the ticket updated as you progress
- Use ticket key in commit messages for traceability
- Check comments for clarifications from stakeholders
Next Steps
After loading ticket:
- Use ticket-comments skill to see discussion history
- Use ticket-update skill to modify fields
- Use ticket-transition skill to change status
