Emma ThorpeandClaude Opus 4.8
a97b433a7b
Vendor the auto-memory directory into the repo (claude/memory/) and symlink it read-only into ~/.claude/memory. Recall keeps working; the runtime "save a memory" path no longer writes there. CLAUDE.md instructs Claude to add/change memories in this repo and rebuild instead, so the flake stays the single source of truth. README documents the split. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.0 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| jira-tooling | Jira MCP tool quirks — comment markdown, transitions, link direction, WSP transition IDs |
|
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.