playbooks

home / skills / thebushidocollective / han / my-tickets

my-tickets skill

/plugins/services/jira/skills/my-tickets

This skill shows all Jira tickets assigned to you, grouped by status, with key, summary, priority, and last update for quick triage.

npx playbooks add skill thebushidocollective/han --skill my-tickets

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
789 B
---
name: my-tickets
description: Show all Jira tickets assigned to you
---

# my-tickets

## Name

jira:my-tickets - Show all Jira tickets assigned to you

## Synopsis

```
/my-tickets [arguments]
```

## Description

Show all Jira tickets assigned to you

## Implementation

Retrieve and display all Jira tickets currently assigned to you.

Use the Atlassian MCP tool `atlassian_search_issues` with JQL:

```
assignee = currentUser() AND status != Done
```

Group the results by status and display in a clear table format:

| Key | Summary | Status | Priority | Updated |
|-----|---------|--------|----------|---------|

Include:

- Ticket key (e.g., PROJ-123)
- Summary (truncate if too long)
- Current status
- Priority
- Last updated date

Show count of tickets by status at the end.

Overview

This skill shows all Jira tickets currently assigned to you and not marked Done. It gathers issue key, summary, status, priority, and last updated date, then presents them in a clear table grouped by status. A summary of counts per status is included for quick triage.

How this skill works

The skill queries Jira using a JQL that selects issues where the assignee is the current user and status is not Done. Results are grouped by status and formatted into a concise table with the columns: Key, Summary, Status, Priority, and Updated. Long summaries are truncated for readability and counts by status are displayed at the end.

When to use it

  • You want a quick overview of all active Jira work assigned to you.
  • Preparing for a daily standup and need to list current items by status.
  • Triaging or prioritizing work without opening the Jira UI.
  • Checking which assigned tickets were recently updated.

Best practices

  • Run the command at the start of your workday or before standups for up-to-date context.
  • Use the table to identify blockers by scanning statuses and recently updated items.
  • Open individual tickets from the list when you need full details or to change status.
  • Filter or refine JQL separately if you need project-specific or time-bound views.

Example use cases

  • Get a grouped list of all assigned tickets to prepare your daily plan.
  • Quickly count how many in-progress vs. in-review tickets you own.
  • Spot recently updated tickets that may require immediate attention.
  • Export or copy the table into a report or status message for your team.

FAQ

Which tickets are returned?

Issues where the assignee is the current user and status is not Done.

Can I see completed tickets?

By default completed (Done) tickets are excluded; adjust the JQL if you need them.

How are long summaries handled?

Summaries are truncated to keep the table readable; open the ticket for the full text.