jira-tracker
The Jira adapter for issue-tracker-core — lifecycle, JQL and epic hygiene.
Install
/plugin marketplace add https://catylai.com/marketplace.json/plugin install jira-tracker@catylai
Install issue-tracker-core alongside this. The core holds the discipline —
the gate requiring a real, scoped, assigned issue before any code is written, a
status vocabulary where a state is a claim about reality, and the rule that the
tracker is the durable record and the chat is not. This plugin supplies the Jira
calls that carry it out.
It is the one adapter where the core's default ticket pattern works unchanged.
Jira keys already match [A-Z][A-Z0-9]+-[0-9]+, so a branch name carries a
recoverable key with no configuration, where the GitHub adapter had to solve that
problem from scratch.
Every numeric identifier is treated as configuration rather than content. Issue type ids, transition ids, custom field ids and the Cloud ID all differ per instance, so the skills tell you how to discover your own through documented endpoints instead of shipping values that would be wrong for everyone but one organisation. That is the core's stated reason for existing.
Covers the issue lifecycle end to end, JQL for triage and orphan sweeps as live queries rather than cached inventories, and epic and parent hygiene — including the fact that Jira's hierarchy genuinely differs between company-managed and team-managed projects, which is the detail that makes a generic parent sweep wrong half the time.