Connect Jira
Connect Jira Cloud to a project, choose the project and issue type new issues land in, and push a theme into your backlog in one click.
Connect Jira Cloud and every theme gets a Create Jira issue button that puts the case into the Jira project and issue type you nominated.
Before you begin
- Role: project Editor or Lead. A workspace Admin is a lead on every project.
- In Jira: a Cloud site, and an account that can create issues in the project you want.
- To hand: your site URL, that account's email address, and an Atlassian API token.
- Time: five minutes.
What Adduce sends
One issue per theme, on your click, and nothing else. The body is converted to Jira's own rich-text format, so it arrives formatted rather than as raw markdown.
| In the issue | What it is |
|---|---|
| Summary | The theme's name, trimmed to 255 characters |
| Opening quote | The verdict — recommended, monitor, or not needed — and the reasoning behind it |
| Summary line | Evidence and source counts, strength as a percentage, and sentiment |
| Quotes | Up to five pieces of evidence, each with who said it and a link to it |
| Related findings | Each finding's title and its confidence |
| Footer | A link back to the theme in Adduce |
Permissions the token needs
An Atlassian API token acts as the account whose email sits beside it, so it can reach whatever that person can. Adduce uses it for four things:
| Call | Why |
|---|---|
| Read your own account | Confirm the token works, and name the connection |
| List projects | Fill the Jira project picker |
| List issue types | Fill the Issue type picker for the project you chose |
| Create an issue | Create the issue |
Nothing is read from Jira into the project. Adduce never reads your existing issues, boards or comments.
Steps
In Jira, go to id.atlassian.com and open Security → API tokens, then create a token. Copy it; Atlassian will not show it again.
In Adduce, open the project, choose Sources, and scroll past the sources list to Issue trackers.
On the Jira card, enter the Jira site URL — the https://your-team.atlassian.net address, with no path after it — then the Atlassian account email and the API token, and choose Connect Jira. Adduce calls Jira before it stores anything; a refusal is reported under the field and nothing is saved.
The card now asks where issues land. Choose a Jira project, then an Issue type from that project's own list, and choose Save destination. Jira is the only tracker that needs this: Linear and GitHub ask per issue instead.
Open a theme and choose Create Jira issue. There is no picker — the issue goes straight to the destination you saved.
The button becomes the issue key and opens it in Jira. If the issue could not be created, the button reads Retry Jira issue instead.
When Adduce sends
Only when you click. Creating an issue is never retried automatically, because a retried create is a second issue. Reads — the project and issue-type lists — do retry up to three times when Jira is rate limiting or briefly unavailable.
A theme that changes after its issue was created does not update the issue, and closing the issue in Jira does not change the theme.
Disconnect or replace credentials
On the Jira card choose Disconnect. The stored token is deleted, the saved destination goes with it, and the create-issue button disappears from every theme in the project; issues already in Jira are untouched. To rotate a token, disconnect and connect again.
If it did not work
Why does it say there is no Jira Cloud API at that site URL?
The address is reachable but it is not a Jira Cloud site. Use the bare https://your-team.atlassian.net origin — not a board URL, not a path, and not a server address on a private network, which is refused outright.
Why were the credentials rejected?
Jira answered, and said no. The email and the token must belong to the same Atlassian account, and the token must not have been revoked. Create a fresh token and enter both again.
Why does a theme show Choose where Jira issues go instead of a create button?
Jira is connected but no destination is saved yet. The button takes you to Sources, where the Jira card carries the Jira project and Issue type pickers.
What's next
Connect Linear
Connect Linear to a project so a theme can be pushed into your backlog as an issue, carrying its verdict, its numbers and its quotes.
Connect GitHub Issues
Connect GitHub to a project with a fine-grained token so a theme can be pushed into a repository as an issue, with its evidence and quotes.