22 lines
1.0 KiB
Markdown
22 lines
1.0 KiB
Markdown
|
---
|
||
|
|
name: jira-tooling
|
||
|
|
description: Jira MCP tool quirks — comment markdown, transitions, link direction, WSP transition IDs
|
||
|
|
metadata:
|
||
|
|
type: feedback
|
||
|
|
---
|
||
|
|
|
||
|
|
**Comment markup:** `addCommentToJiraIssue` `commentBody` renders as Markdown — use `###` headings, `**bold**`, backtick `code`, `1.` / `-` lists. Do NOT use wiki markup (`h3.`, `{{code}}`, `_italic_`, `#` numbered) — it renders literally.
|
||
|
|
|
||
|
|
**Transitions:** `transitionJiraIssue` may fail if the issue lacks an assignee. Set assignee first via `editJiraIssue` when a transition errors on assignee requirement.
|
||
|
|
|
||
|
|
**Issue link direction:** For `createIssueLink`, "X is blocked by Y" means `inwardIssue=Y` (the blocker), `outwardIssue=X` (the blocked), `type.name="Blocks"`. Inward = the side the link points _from_; outward = the side it points _to_.
|
||
|
|
|
||
|
|
**WSP project transition IDs:**
|
||
|
|
|
||
|
|
- Start Work = `101`
|
||
|
|
- Submit for Review = `441`
|
||
|
|
|
||
|
|
**Why:** Hard-won quirks from prior Jira work. Cuts trial-and-error.
|
||
|
|
|
||
|
|
**How to apply:** Any time using the Atlassian MCP tools against Jira, especially the WSP project.
|