Jira
Create Jira Cloud issues from feedback, using an Atlassian API token.
Pro and above. Jira Cloud only. Setup needs four values.
Connect
Create an API token
Go to id.atlassian.com/manage-profile/security/api-tokens → Create API token. Name it "Annot8" and copy the value — it's shown once.
Gather the rest
| Field | Example | Where |
|---|---|---|
| Domain | yourcompany.atlassian.net | Your Jira URL, without https:// |
| Project key | PROJ | The prefix on your issue keys, e.g. PROJ-142 |
| Your Atlassian email | you@company.com | The account the token belongs to |
Connect in Annot8
Integrations in the sidebar → Jira → enter the API token, domain, project key, and email → Connect, then Test.
Enable it per project
Project → Integrations → toggle Jira on.
Two ways issues get created
Automatically, for every new thread on a project where Jira is enabled. The
issue is created as a Task, titled [Feedback] <comment>, with the author,
the comment, and a link to the page in the description.
On demand, by right-clicking a thread and choosing Integrations → Create Jira issue — which carries the full thread context: page path and URL, issue type, priority, status, expected and actual behaviour, and the element selector.
Enabling Jira for a project turns every piece of feedback into a Jira issue. Point it at a dedicated intake project, or leave it off and create issues on demand.
Permissions
The API token acts as the account that created it. That account needs Create
Issues permission on the target project, and its email has to match the one
you entered — Jira's basic auth is email:token and a mismatch reads as bad
credentials rather than a permissions error.
Different Jira projects per Annot8 project
Set a per-project override with a different project key under Project → Integrations.
Troubleshooting
401 or "unauthorized". Almost always an email that doesn't match the token's account, or a revoked token.
404 on create. Wrong project key, or the account can't see that project.
"issuetype is required" or similar. The target project's workflow doesn't have a Task issue type. Add one, or point the integration at a project that uses the default scheme.
Domain rejected. Enter the bare hostname — yourcompany.atlassian.net — not
a full URL and not a trailing slash.