manage-ticketslisted

Create, edit, search, transition, close, and triage Jira tickets via the Atlassian MCP. Use when asked to file a bug, request a feature, create a task, log a defect, search the backlog, triage findings into the tracker, edit ticket fields, transition status, or manage Jira work items. Also use when the user says 'create a Jira issue', 'file a bug', 'open a ticket', 'add to backlog', 'search Jira', 'close ticket', 'move to Done', or names any Jira issue key (e.g. 'PROJ-123'). Also use for read-only backlog sweeps: which ticket to pick up next, what is unblocked, what blocks a given key, how many issues are open. Handles type discovery, parent linking, label assignment, duplicate detection via JQL, status transitions, issue-link creation, and large queries that overflow the tool output limit. Defers all field-content formatting to the `jira-syntax` skill. Do NOT use for pull requests, changelog entries, non-Jira trackers (GitHub Issues, Linear, GitLab), or managing local TODO.md.
sergeyklay/.agents · ★ 5 · AI & Automation · score 80

Install: claude install-skill sergeyklay/.agents

# Managing Jira Tickets Manage Jira tickets via the Atlassian MCP. Every ticket must be self-contained, professional, and actionable without prior context. The skill applies only to Jira sites the Atlassian MCP is connected to; if the MCP is unavailable, stop and tell the user. ## Prerequisites 1. Atlassian MCP server is available. MCP is the only path to Jira - never `curl`, never bare HTTP, never `gh`. 2. `jira-syntax` skill is loaded before composing any field content. Jira description and comment fields are wiki markup, not Markdown. ## Discover project metadata (run first) Before any create, edit, search, or transition operation, fetch the live metadata for the target site and project: | Need | Tool | |-------------------------------------|-----------------------------------| | Jira site `cloudId` | `getAccessibleAtlassianResources` | | Visible projects and their keys | `getVisibleJiraProjects` | | Types accepted by chosen project | `getJiraProjectIssueTypesMetadata`| | Required fields for a chosen type | `getJiraIssueTypeMetaWithFields` | | Site-wide issue link types | `getIssueLinkTypes` | | Valid transitions for an issue | `getTransitionsForJiraIssue` | | Resolve display name to account id | `lookupJiraAccountId` | Use the values verbatim. Never memorize project keys, type names, transition IDs, label names, or account IDs