Connect Jira Cloud

YakShaver can create issues in Jira Cloud for shaves recorded with YakShaver Anywhere. It connects through Atlassian's remote MCP server, so there is no app to register and no credentials to create. Your Atlassian organisation admin does have to allow YakShaver first (step 1).

Jira Cloud only. Jira Data Center and Jira Server are not supported. See Limitations.

1. Allow YakShaver in your Atlassian organisation

Atlassian's MCP server only accepts a sign-in that returns to a domain it trusts: one on its supported list, or one your organisation has added. YakShaver is not on that list, so an Atlassian organisation admin has to add it, once per organisation. This is not a Jira project setting.

1. Go to Atlassian Administration and select your organisation.
2. Open Connectors → Atlassian MCP server. Some Atlassian articles call this Rovo → Rovo MCP server → Domain settings, so your menu may differ.
3. Click Add domain and enter https://api.yakshaver.ai/**
4. On the Permissions tab, allow Jira for Read, Write and Search. YakShaver reads projects and create screens, creates issues, and searches for issues it has already filed.
5. If your organisation uses IP allowlists, allow YakShaver's outbound IP addresses too. Contact us for the current list, because they can change when the service scales.

If you skip this step, Atlassian stops the connection on its own page. Nothing reaches YakShaver, so the portal cannot show an error. Use the wording on Atlassian's page to find the cause in Troubleshooting.If a saved domain does not take effect, remove it and add it again, then retry in a private window.

2. Connect Jira

1. In the YakShaver portal, go to Settings → Integrations. You need the Admin role.
2. Click Connect on the Jira row and read the prerequisites.
3. Complete the Atlassian consent screen, choosing the site you want to file to.

Atlassian signs you in with whichever account this browser is already using. To connect a different account, sign out of Atlassian first or use a private window.

Use a dedicated Jira service account.The connection acts as whoever completes this step. Every issue YakShaver creates is attributed to them, and the connection stops working when they leave or lose access. Connecting with a personal account works, and then breaks at the worst time.The account needs a Jira licence on the site and permission to create issues in your projects.

3. Point a project at Jira

1. In the portal, open the project and click Edit.
2. Under Work item destination, choose Jira.
3. Pick the site, then the project.
4. Click Save destination.

You don't choose an issue type. YakShaver decides for each shave from the recording: a title starting with 🐛 files a Bug, and anything else files a Story, Task or Feature, whichever the project has.

When you save, YakShaver checks the create screens of those issue types. If one needs a field YakShaver cannot fill, or has no Labels field (see Limitations), the save is refused with the type and the problem named. You find out now, not when a shave fails.

To undo, click Use backlog URL instead.

What lands in the issue

Limitations

Platform

• Jira Cloud only. Atlassian's MCP server cannot reach Jira Data Center or Jira Server.
• Jira Service Management projects are not supported. They need a request type YakShaver cannot supply, so they are hidden from the project list.
• Sub-task issue types are excluded. A sub-task needs a parent, and a shave cannot choose one.
• The issue type needs a Labels field on its create screen. Labels are how YakShaver recognises an issue it has already created, so a type without them is refused when you save the destination, instead of being allowed to file duplicates.

Content

• Summaries are cut at 255 characters, and line breaks become spaces.
• Screenshots are linked images, not attachments. Atlassian's MCP server cannot upload attachments.
• The recording is linked, not attached.
• Creating an issue triggers the project's notification scheme, so watchers and the project lead get an email.

Identity and connection

• Issues are attributed to the account that connected Jira (see step 2).
• The connection expires after 90 days without use. YakShaver refreshes it each time it files, not on a schedule, so if nothing is filed for 90 days an admin has to reconnect. The portal asks you to reconnect when that happens, as it does when someone revokes access.
• Issue keys change when an issue moves between projects. YakShaver also keeps the issue's permanent ID where Atlassian provides one, so its links keep working.
• Atlassian can change its MCP server at any time. If a tool YakShaver needs is renamed or removed, YakShaver tells you which one, but it may need an update before it can file again.

Scope

• Jira works with YakShaver Anywhere only. Teams and browser extension shaves on the same project still use the project's Backlog URL, which supports GitHub and Azure DevOps only, and fall back to email. A Backlog URL that points at Jira is rejected.

Troubleshooting