Kognita.Jira integration
Connect your Atlassian account to let your AI agent read Jira issues and tickets alongside your code — in the same conversation.
What this enables
- Ask your AI agent to pull context from a Jira ticket while reviewing or writing code
- Trace a bug report back through the codebase without switching tools
- Reference acceptance criteria from a story when generating or testing a feature
- Summarize open issues in a project without leaving your editor
- Compare planned ticket scope with the system behavior that already exists before a ticket is written
Before scoping tickets
Jira becomes much more useful when it is connected to the actual codebase. Product owners, scrum masters, QA, and support leads can ask what the system already does before turning an idea or customer complaint into a ticket. Kognita can use Jira context and indexed code together, so the answer is grounded in both the requested work and the implementation that already exists.
Check existing behavior
Ask whether a workflow, validation rule, role permission, or edge case already exists before creating duplicate work.
Find affected services
See which services, screens, jobs, APIs, and data models a proposed ticket is likely to touch.
Improve acceptance criteria
Turn vague requirements into testable criteria using the current implementation and related Jira history.
Spot release risk early
Surface dependencies, ownership, and prior related tickets while the ticket is still cheap to change.
Before you start
You need an Atlassian account with access to at least one Jira project. The free tier is sufficient. You also need a Kognita project already set up — if you haven't done that yet, start in the dashboard.
Setup guide
Find your Atlassian workspace URL
Open any Jira issue or board in your browser. Look at the address bar — your workspace URL is the domain shown there. It looks like yourcompany.atlassian.net.
Copy just the domain part. Do not include https:// or anything after the domain — for example, if the full URL is https://acme.atlassian.net/jira/software/projects/…, the workspace URL is simply acme.atlassian.net.
Note the email on your Atlassian account
You'll also need the email address associated with your Atlassian account. This is the email you use to sign in to atlassian.com. Kognita uses it together with the API token to authenticate requests to Jira.
Recommended: create a dedicated Atlassian account for Kognita (e.g. kognita@yourcompany.com) and invite it to your workspace. Any comments or tickets the AI agent creates will appear under that account, keeping a clear audit trail separate from your personal activity.
Open your Atlassian account settings
Click your avatar in the top-right corner of any Atlassian product and choose Manage account. This takes you to id.atlassian.com.
Navigate to Security → API tokens
In the left sidebar, click Security. Scroll to the API tokens section and click Create and manage API tokens.
Create a new API token
Click Create API token. Give it a descriptive label — for example Kognita — so you can identify it later. Click Create.
Copy the token
Click Copy to clipboard. Store it somewhere safe — Atlassian will not show the token again once you close this dialog.
Connect Jira in Kognita
Go to your Kognita dashboard and click MCPs in the left sidebar. Find your project, then click Connect next to Jira.
Fill in the three fields:
- Atlassian domain — e.g. yourcompany.atlassian.net
- Atlassian email — the email you use to sign in
- API token — the token you just copied
Click Save token. Kognita verifies the credentials against Jira before saving — you'll see an error inline if anything is wrong.
Tip: create a dedicated Atlassian account
We recommend creating a separate Atlassian account specifically for Kognita — for example kognita@yourcompany.com. Invite it to your Jira workspace and generate the API token from that account. This way, comments posted and tickets created by the AI agent appear under a clear bot identity rather than your personal account, and you can revoke access independently at any time.
Security note
Your Jira credentials are stored securely on Kognita's servers and are only used to authenticate requests to the Jira API on your behalf. You can disconnect at any time from the MCPs panel, which immediately removes the stored credentials.
Troubleshooting
Where do I find my workspace URL?
Open any Jira issue or board. The workspace URL is the domain in your browser address bar — for example yourcompany.atlassian.net. Copy just the domain without https:// or any trailing path.
I get an "Invalid Jira credentials" error
Double-check that the domain, email, and token all match the same Atlassian account. A common mistake is using a personal email when the workspace is on a company account, or copying only part of the token.
My AI agent says it cannot access Jira
Check that the credentials were saved correctly — go to MCPs in the dashboard and look for the green "connected" badge next to Jira. If it's not there, click Connect and enter your domain, email, and token again.
I need to use a different Jira account
Click Disconnect in the Jira section of MCPs, then Connect again with the new credentials. Credentials are stored per project, so you can use different accounts across projects.