Connect Jira
Keel reads the status of the Jira issues linked to a person’s onboarding or offboarding once a day. The status shows in the Tickets panel on the person’s page, and the Leaver tickets resolved within 7 days check looks at every offboarding issue. Linking tickets is described in Onboarding records.
Jira API tokens carry the permissions of the account that created them. Keel sends only read requests, only to the site you connect, and stores the token encrypted.
Time: about 5 minutes.
Before you start
Section titled “Before you start”- In Jira: an Atlassian account that can browse the projects your onboarding and offboarding issues live in. A dedicated account with only the Browse projects permission is the safest choice.
- In Keel: you are an owner or admin of the workspace.
Create the API token
Section titled “Create the API token”- Sign in to id.atlassian.com as that account. The link opens Security > API tokens.
- Click Create API token.
- Name:
keel-evidence. Pick an expiry date your policy allows. - Click Create, then copy the token. Atlassian shows it only once.
Connect it in Keel
Section titled “Connect it in Keel”- In Keel, open Integrations, find the Jira card and click Connect.
- Under Credentials, fill in:
- Site: your Jira Cloud address, for example
acme.atlassian.net. - Account email: the email of the account that created the token.
- API token: the token you copied.
- Site: your Jira Cloud address, for example
- Click Save connection.
Evidence connector connected. Its credential is stored encrypted. means it worked.
See the first findings
Section titled “See the first findings”Open the Findings tab and click Collect now, or wait for the next daily run.
- An offboarding issue passes when Jira resolved it within 7 days of its creation, or when it is still open and inside those 7 days.
- It fails when it was resolved later, or is still open after 7 days.
- An issue on a different Jira site than the one connected is listed as unreadable. Keel never sends the token anywhere else.
To leave a person out of the check, put them out of scope from Affected items.
Troubleshooting
Section titled “Troubleshooting”| What you see | What to do |
|---|---|
| Check the connection details and try again. | The site, email or token is wrong, or the token has expired. Create a new token and connect again. |
| An issue shows Could not read the ticket (HTTP 404) | The account cannot browse that project, or the issue was deleted. Give the account Browse projects on it. |
Rotate or remove access
Section titled “Rotate or remove access”- Rotate: create a new token, disconnect and reconnect in Keel, then revoke the old token on the same API tokens page.
- Remove: click Disconnect in Keel, then revoke the token.