Jira Cloud plugin

Opens a Jira issue for each Mushi Mushi bug report and keeps it in step as the report moves to fixed.

Setup (Mushi Mushi Cloud, no code)

At id.atlassian.com → Security → API tokens, create an API token.
In the Mushi Mushi console: open the Integrations page, find Jira, and enter your Jira base URL (e.g. https://acme.atlassian.net), the Atlassian email that owns the token, the token, and the project key (e.g. BUG).
Click Save, then Test connection.

Mushi Mushi opens and resolves the Jira issues itself; you do not need the npm package.

Self-hosted plugin

@mushi-mushi/plugin-jira is a library for doing the same from your own server with Jira OAuth 2.0 (3LO): buildAuthorizeUrl, exchangeCode, refreshTokens and createJiraPluginHandler. See its README for the code. The console’s Marketplace has no Jira listing, so you can’t install it from the console. On a Mushi Mushi server you run yourself, add a plugin_registry row for it and install it like any listed plugin.

Event	Action
`report.created`	Create a Jira issue under `jiraProjectKey`, labelled with category and severity (`unknown` here, since triage hasn’t run yet)
`report.status_changed`	Run the Jira transition from `statusToTransition` (defaults: pending/classified/grouped → To Do, fixing → In Progress, fixed/dismissed → Done)
`fix.applied`	Comment `Mushi fix applied: <PR link>`. `fix.applied` carries no summary, so none is added

The report → issue mapping is kept in memory, so after a restart status changes and fix comments for older reports are skipped.