Jira Integration
Work Jira tickets from inside your Muse session: fetch requirements, extract acceptance criteria, comment, transition status, via MCP or direct REST.
- What
- Work Jira tickets from inside your Muse session: fetch requirements, extract acceptance criteria, comment, transition status, via MCP or direct REST.
- Cost
- Free
- Needs
- Use "Jira Integration" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a Jira bridge for the AI coding workflow, with two paths. Option A, recommended: the mcp-atlassian MCP server wired into the MCP config with JIRA_URL, JIRA_EMAIL, and JIRA_API_TOKEN in the environment, exposing search, create, update, comment, and transition tools directly to the agent. Option B: direct Jira REST API v3 calls via curl or helper scripts, with the same environment variables and credentials kept out of command lines and source. The skill covers fetching a ticket to understand requirements, extracting testable acceptance criteria, adding progress comments, transitioning status from To Do to In Progress to Done, linking merge requests and branches to issues, and searching by JQL. Security guidance is explicit: never hardcode secrets, prefer environment or a secrets manager, keep tokens out of committed files. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: you need a real Jira instance and an API token from id.atlassian.com; the skill assumes you already have Jira access, it does not create it. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Jira Integration" with your Muse. Prerequisites: a Jira instance you can access, and an API token from https://id.atlassian.com/manage-profile/security/api-tokens. Store JIRA_URL, JIRA_EMAIL, and JIRA_API_TOKEN in your environment or a secrets manager, never in source. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/jira-integration/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Fetch ticket [KEY] and extract testable acceptance criteria" or "Transition [KEY] to In Progress and add a progress comment." 3. Work with Muse through the ticket; it reads requirements and writes back status and comments. Tip: the MCP server (uvx mcp-atlassian) is the smooth path; direct REST is the fallback when MCP is unavailable. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste real API tokens into a chat.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.