RHDH Jira API

One home for talking to Jira. The command syntax, the field IDs, the query patterns, and the workflow rules live here so that the create, refine, update, and sprint skills carry none of their own copies.

This skill reads. It never decides what to file and never approves a write — though it does define exactly what a write costs, because the payload shapes are here.

Route by question

Load the one branch the question needs.

The two traps that produce wrong answers

Both fail silently, and both have burned this pack before.

Default page size is 30. Rows past the thirtieth are dropped with no warning, so a query that should return 140 issues quietly returns 30 and every count built on it is wrong. Pass --limit 500 or --paginate on every bulk search, and use --count first when the total matters.

Custom fields are absent unless you ask for them. search --json and view KEY --json return only assignee, issuetype, priority, status, and summary. Story Points, Team, Size, and Sprint come back empty — which looks exactly like a field nobody set. Enrich with scripts/parse_issues.py --enrich or view KEY --fields '*all' --json before claiming any of them is missing.

A field you could not retrieve is reported as unretrieved, never as empty.

Bundled scripts

Run these from this skill's directory.

Stdlib only. Another skill invokes /rhdh-jira-api by name and lets this skill run them; it never reaches into this directory by path.

Writes

This skill does not perform writes, but the payloads live here because the field IDs do. It hands the caller a command or a payload, never an effect. Whichever skill owns the verb invokes /mutation-gate and runs it from there.

Credentials never appear in an argument, a preview, a log, or the answer. A command built here takes its credential from acli's own store, the local token-file adapter (in-process, never printed), or the authenticated host adapter at run time, so nothing this skill hands back carries one.

Boundary with the neighbouring skills

• Opening new work is /rhdh-jira-create.
• Judging whether existing work is ready is /rhdh-jira-refine.
• Changing a field, status, assignee, comment, or link on a known key is /rhdh-jira-update.
• Sprint carryover, velocity, and next-sprint capacity are /rhdh-jira-sprint-plan; the end-of-sprint summary is /rhdh-jira-sprint-report.
• Whether a team can fit rhdh-X.Y-candidate Features through Code Freeze is /rhdh-release-capacity-plan.
• Issue templates, the grill matrix, sizing scales, and decomposition rules are /rhdh-jira-authoring.
• What is still open against a release is /rhdh-release-status.
• Creating or repairing a credential is /setup-rhdh-skills.

Completion

A read is complete when every field the answer asserts was actually fetched. Report the exact JQL or command used, the number of issues returned, and whether the result was truncated — a truncated result is an incomplete answer, not a finding. Say which adapter produced each fact, acli or the host adapter. A field the API could not supply is named as unretrieved rather than reported as empty or carried over from an earlier query.