Our review

Fetches complete details of a Jira ticket (summary, description, status, priority, assignee, etc.) to understand task context.

Strengths

Provides a structured overview of the ticket (status, priority, type) in a single command.
Includes creation and update dates along with linked issues for broader context.
Integrates into a ticket-driven development workflow, making it easy to load context before implementing.
Supports multiple output formats (text, JSON, markdown) for flexibility.

Limitations

Requires the 'aide' tool to be installed and configured with proper Jira access.
Does not handle comments or discussion history (a separate 'ticket-comments' skill is needed for that).
Depends on the Jira API; may fail if the ticket is inaccessible or permissions are insufficient.

When to use it

Use this skill when you need to view the details of a Jira ticket before starting a task, to understand requirements or check status.

When not to use it

Do not use it to modify a ticket, comment, or change its status – other skills are dedicated to those actions.

Examples

View ticket PROJ-123

Show me the full details of Jira ticket PROJ-123, including status, priority, and assignee.

Understand task context

What is the ticket TASK-456 about? I need to understand the requirements before I start working on it.

Load current sprint ticket

Load the Jira ticket for our current sprint issue so I can review the acceptance criteria.

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

View Jira Ticket Details

Recommended for