Skip to content

docs(rhdh-jira): add Gotcha #19 — MCP create_jira_issue does not support ADF #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
christoph-jerolimov merged 1 commit into from
Jul 29, 2026
Merged

docs(rhdh-jira): add Gotcha #19 — MCP create_jira_issue does not support ADF #76

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions skills/rhdh-jira/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -164,6 +164,7 @@ Load only what the current task requires.
16. **Feature→Epic child links use Parent Link, not issuelinks.** Cross-project parent-child relationships (RHDHPLAN Feature → RHIDP Epic) use the `Parent Link` field (`customfield_10018`), not `issuelinks`. To find child Epics of a Feature, use JQL: `project = RHIDP AND type = Epic AND "Parent Link" = RHDHPLAN-XXX`. Checking `issuelinks` will show zero results and produce false "no child Epics" reports.
17. **REST `/rest/api/3/search` returns 410 Gone.** This endpoint has been removed. Use POST to `/rest/api/3/search/jql` with body `{"jql": "...", "fields": [...], "maxResults": N}` instead. This only affects direct REST calls — `acli search` still works.
18. **`acli workitem create` does not support `--priority`, `--component`, or `--yes`.** These flags exist on `edit`, `transition`, and `assign` but not on `create` — passing them causes "unknown flag" errors. After creating an issue, set priority, components, size (`customfield_10795`), and parent link (`customfield_10018`) together in a single `PUT /rest/api/3/issue/{key}` call.
19. **MCP `create_jira_issue` does not support ADF.** The MCP tool's `description` parameter accepts a plain string, which Jira wraps in a single paragraph node — markdown syntax (`## Heading`, `**bold**`, `- [ ] task`) renders as literal characters. For formatted descriptions (headings, lists, code, links, task items), always use `acli jira workitem create` with `--description-file` pointing to ADF JSON. Use the MCP tool only for quick unformatted issues where plain text is acceptable.

## Error Handling

Expand Down
Loading