Jira is in beta. It has been tested against recorded responses, not yet against a real
account, so tell your MITHUNAI contact if a sync does not read what you expect.
What you need
- A Jira Cloud site, at an address like
https://your-company.atlassian.net. Jira Data Center and sites on your own domain are not supported. - An Atlassian account that can browse the projects you want read.
- The owner or admin role in your MITHUNAI organisation.
1. Create the API token in Atlassian
If you already saved an Atlassian connection for Confluence on the same site, skip to step 3: one connection reads both. Signed in to Atlassian as the account MITHUNAI will read as:- Go to id.atlassian.com/manage-profile/security/api-tokens.
- Select Create API token. If you see a choice, choose the plain API token, not the one with scopes: MITHUNAI does not support scoped tokens yet.
- Name it so you will recognise it later, such as
MITHUNAI. - Choose an expiration date, from 1 to 365 days. Note the date: you will replace the token before then.
- Select Create, then Copy to clipboard.
2. Save it in MITHUNAI
- In the console, open Knowledge → Sources and choose Connect source.
- Under Issues and support, choose Jira.
- If you have no Atlassian connection yet, the form to add one is open. Fill in:
- Connection name: such as
Engineering Atlassian. - Site address: such as
https://your-company.atlassian.net. It cannot be changed later. - Account email: the email of the Atlassian account the token belongs to.
- Token: the API token you copied.
- Connection name: such as
- Choose Save connection. The token is stored encrypted and is never shown again.
3. Choose what to read
- Name: what the source is called in your list.
- Projects: the short code at the start of each issue key, separated by commas.
ENG-42is in projectENG. At least one is needed. - Under Change filters: Resolved issues only reads only issues whose status is in Jira’s Done category, and Maximum issues is from 1 to 5,000, 500 by default.