mit einem Klick
capp-get-jira-info
Centralised CAPP Jira metadata — cloud ID, field IDs, transition IDs, issue type IDs, link types. Invoke before any Jira MCP call to skip redundant discovery API calls and ensure consistent field references.
Menü
Centralised CAPP Jira metadata — cloud ID, field IDs, transition IDs, issue type IDs, link types. Invoke before any Jira MCP call to skip redundant discovery API calls and ensure consistent field references.
| name | capp-get-jira-info |
| description | Centralised CAPP Jira metadata — cloud ID, field IDs, transition IDs, issue type IDs, link types. Invoke before any Jira MCP call to skip redundant discovery API calls and ensure consistent field references. |
| Level | Meaning | Examples |
|---|---|---|
| Stable | Changes only via admin action; safe to hardcode | Cloud ID, project ID/key, field IDs, issue type IDs, link type IDs |
| Workflow-dependent | Changes if the Jira workflow is edited | Transition IDs, status IDs, status category mappings |
| Dynamic | Changes frequently; always query live | Sprint IDs, user account IDs, board IDs |
| Key | Value |
|---|---|
| Cloud ID | 3fa693cf-5995-4779-a4db-6af578c534d3 |
| Project key | CAPP |
| Project ID | 14798 |
Pass cloudId: "3fa693cf-5995-4779-a4db-6af578c534d3" to every Atlassian MCP tool call.
| Type | ID | Subtask? | Notes |
|---|---|---|---|
| Task | 21348 | No | Default for general work |
| Bug | 21349 | No | |
| Story | 21350 | No | Only type with Story Points |
| Epic | 21351 | No | |
| Subtask | 21352 | Yes | Created under a parent issue |
| Spike | 25025 | No | |
| Unplanned Work | 25026 | No | |
| Design Task | 30779 | No | |
| Retro Action | 32181 | No |
When creating issues pass issueTypeName (e.g. "Task") — the MCP tool resolves the name. Use the numeric ID only when an API requires it explicitly.
| Field | ID | Available on | Format notes |
|---|---|---|---|
| Dev Notes | customfield_26991 | Task, Bug, Story, Epic, Spike, Unplanned Work, Design Task — NOT Subtask | Rich text. Write with contentFormat: "markdown". Read with responseContentFormat: "markdown" |
| Story Points | customfield_10016 | Story only | Number |
| Sprint | customfield_10020 | Most types | Dynamic — always query live |
| Flagged | customfield_10021 | Most types | Option ID 10019 = Impediment |
| Field | Task | Bug | Story | Subtask | Epic | Spike |
|---|---|---|---|---|---|---|
| Dev Notes | ✅ | ✅ | ✅ | ❌ | ✅ | ✅ |
| Story Points | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ |
| Sprint | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ |
| Status | Category |
|---|---|
| To Do | To Do |
| In Progress | In Progress |
| In Review | In Progress |
| In Test | In Progress |
| Ready for Release | Done |
| Done | Done |
| From → To | Transition Name | ID |
|---|---|---|
| To Do → In Progress | Begin Work | 2 |
| In Progress → In Review | In Review | 3 |
| In Review → In Test | In Test | 4 |
| In Test → Ready for Release | Ready for Release | 5 |
| In Progress → Done | Done | 6 |
| In Test → Done | Done | 6 |
| In Test → In Progress | Failed Testing | 7 |
| In Review → In Progress | Failed Review | 8 |
| Any → Won't Do | Won't Do | 10 |
| In Progress → To Do | ToDo | 11 |
| Done → To Do | ReOpen | 12 |
| Done → In Progress | In Progress | 14 |
Always confirm the issue's current status matches the expected "From" status before using a hardcoded transition ID. Jira transition IDs are only valid from specific statuses. If the current status does not match, consult this map to find the correct transition or fall back to live discovery.
| Name | ID | Inward description | Outward description |
|---|---|---|---|
| Blocks | 10000 | is blocked by | blocks |
| Cloners | 10001 | is cloned by | clones |
| Duplicate | 10002 | is duplicated by | duplicates |
| Relates | 10003 | relates to | relates to |
When creating links with createIssueLink, pass the name (e.g. type: "Blocks"). The inward issue is the blocker; the outward issue is the blocked task.
| Operation | Parameter | Value |
|---|---|---|
| Writing description / Dev Notes / comments | contentFormat | "markdown" |
| Reading issue fields | responseContentFormat | "markdown" |
| Creating issues | contentFormat | "markdown" |
Always pass these parameters explicitly — the MCP default is ADF, which is harder to read and write.
If a hardcoded value fails (e.g. transition returns an error, field is not found):
This protocol avoids both blind trust in stale IDs and unnecessary API calls on every invocation.
These values change too frequently to hardcode:
customfield_10020 on an existing issue, or list sprints from the boardlookupJiraAccountId with search stringcontentFormat/responseContentFormat as specified in the content format tableImport a skill from exactly one GitHub file URL, raw GitHub URL, or single-file gist URL into ~/.agents/skills/. Use when the user wants to add a skill from GitHub content.
Address all review comments on a GitHub pull request. Fixes code, pushes back with evidence, resolves threads after completion, and updates AGENTS.md only when specifically requested. Use after receiving PR review feedback.
Tidy up CaPP git worktrees whose PRs are merged or closed without merging. Scans for directories matching the `<repo>_<TICKET-ID>` worktree convention (e.g. `twinkl-sanity-cms_CAPP-1234`), looks up each worktree's PR via `gh`, classifies by state, flags closed-unmerged PRs, and removes worktrees only after explicit user confirmation. Use when the user asks to clean up worktrees, prune CAPP worktrees, or tidy `~/Development`.
Create well-structured Jira tickets through adaptive interview. Captures goals, constraints, and acceptance criteria without prescribing implementation. Use when creating new work items for the CaPP team.
Implement a Jira ticket by iteratively completing subtasks using TDD. Creates a feature branch, one commit per subtask, and a draft PR. Also handles small well-defined bugs without subtasks. Use when ready to start coding.
Diagnose and fix GitHub Actions CI failures on a pull request. Fixes code issues, validates locally using identified check tiers, and pushes focused fixes. Use when CI is failing on a PR.