Skip to main content

​
Set up for yourself

Works on all plans. Your own connection works in Ask Jamie, Sidekick, briefings, and your own workflows. Jamie signs in with your Atlassian account email and an Atlassian API token.

In Atlassian

  1. Open Atlassian account → Security → API tokens
  2. Click Create API token, give it a name such as Jamie, and choose an expiry date. Don’t choose Create API token with scopes, because Jamie connects to your site address and scoped tokens don’t work there
  3. Copy the token right away. Atlassian shows the token only once

In Jamie

  1. Open Settings → Agent → Connectors
  2. Find Jira and click Connect
  3. In Atlassian site URL, enter the address you see when you are signed in to Jira, such as yourteam.atlassian.net
  4. In Atlassian account email, enter the email of the account that created the token
  5. Paste the token into API key and click Connect. Jamie tests the token with a check that changes nothing in Jira
To test or change the token later, open Jira and click Manage key.
Jamie sees only the projects and issues your Atlassian account can see. Every issue, comment, and status change that Jamie makes shows as yours.
One Atlassian API token works for both Jira and Confluence on the same site. Jamie still asks you to connect each one on its own, so you choose which of the two Jamie can use.

​
Set up for the workspace (admins only)

Needs the Team or Enterprise plan. Only workspace workflows use this connection. Jamie signs in as an Atlassian account that your team creates only for Jamie.

In Atlassian

  1. Create an Atlassian account for Jamie and give it access to the Jira projects it should use. Don’t use your own account
  2. Signed in as that account, create an API token under Atlassian account → Security → API tokens with Create API token
  3. Copy the token right away. Atlassian shows the token only once

In Jamie

  1. Open Settings → Agent → Connectors and select Jira
  2. Under Workspace connection, click Add service account key
  3. Enter the Atlassian site URL and the Atlassian account email of the account you created
  4. Paste the token into Atlassian API token and click Save Jira key
Workspace workflows act as that Atlassian account, not as the person whose meeting it is. So Jamie puts the meeting owner’s name in everything it writes.

​
What Jamie can do

Jamie can:
  • Find projects and search issues by text, status, assignee, or any JQL query
  • Read an issue with its description, status, assignee, and comments
  • File an action item as an issue in the right project, assigned to the person who owns it
  • Comment on an existing issue instead of filing a duplicate, and move it to another status
Jamie can do more than this list. It can’t delete anything in Jira. Try asking: “File the action items from this meeting as Jira issues in the Platform project”

​
Disconnect

  • Your own connection. Open Jira in Settings → Agent → Connectors. Click Manage key, and then click Disconnect.
  • The workspace connection. Under Workspace connection, click Disconnect. Workspace workflows that use Jira pause. They start again when a workspace admin connects Jira again.
To stop the token working everywhere, revoke it in Atlassian account → Security → API tokens.
Last modified on November 2, 2026