PerfCopilot
Get started
HomeDocs
Documentation

Everything you need to write a fair review.

From your first connection to a sealed, delivered review. Set up PerfCopilot, connect your tools, and generate your first cited draft.

Connect Jira

Pulls tickets closed, story points, blocker flags, and open assigned work per employee.

Prerequisites

  • Atlassian Cloud user with ticket-read permission on the projects you want PerfCopilot to see
  • An API token from id.atlassian.com
  • A PerfCopilot admin account (the Connect button is only visible to admins)

1. Generate credentials in Jira

  1. Sign in to https://id.atlassian.com/manage-profile/security/api-tokens.
  2. Click Create API token and give it a label like "PerfCopilot".

📖 Official guide: Manage API tokens for your Atlassian account: Jira's own documentation for creating this credential.

  1. Copy the token value (it is only shown once).
  2. Note your Atlassian base URL (e.g. https://yourcompany.atlassian.net) and the email address of the account that owns the token.

Copy these values; you'll paste them in the next step:

  • base_url (e.g. https://yourcompany.atlassian.net)
  • user_email (the account that owns the token)
  • API token

2. Paste into PerfCopilot

  1. Open Integrations on your PerfCopilot admin.

  2. Find the Jira card and click Connect (or Manage if already configured).

  3. Paste each value into the matching field:

    Field in PerfCopilotValue from step 1
    Base URLhttps://yourcompany.atlassian.net
    User emailyour.name@company.com
    API token<your value>

  4. Click Save.

The Jira credential drawer in PerfCopilot: paste your values, then click Save.
The Jira credential drawer in PerfCopilot: paste your values, then click Save.

3. Verify

Click Test in the drawer. Expected:

✅ Authenticated as your.name@company.com

If you see a red error, jump to Common errors.

Common errors

MessageWhat it usually meansFix
HTTP 401: Basic auth failedToken or email is wrong; Atlassian tokens are tied to one account.Re-generate the token at id.atlassian.com and confirm the email matches that account.
HTTP 404 on /rest/api/3/myselfbase_url is malformed.The base URL should end in .atlassian.net with no trailing slash (e.g. https://yourcompany.atlassian.net).
HTTP 401: <body excerpt>Credentials rejected.Re-check that you copied the full token, no leading/trailing whitespace.

What signals we pull

  • jira: tickets_closed, story_points, blocker flags, and open assigned work

Need a feature you don't see? Tell us →.

PreviousIMAPNext Kisi