Connect Attio to a Jira project
To connect Attio to a Jira project, create a read-only API key in your Attio workspace, then open Project settings, Apps, Attio in Jira and paste it. Selecting Next tests the key and stores it. Answer the remaining setup steps, choose where the card appears, and select Finish setup to switch it on.
#Before you start
You need | Why |
|---|---|
Project administrator rights on the Jira project | Only project administrators can open the Attio settings. Any project type works: service management, software or business. |
Someone who can create keys in Attio | The key is made in Attio, not Jira. It needs |
A site administrator, possibly | Matching on the reporter's email needs Jira's approval to read email addresses, which a site administrator may have to grant in Admin Hub. |
#Steps
In Attio, under Workspace settings, Developers, create an access token with the two read permissions and copy it.
In Jira, open the project and go to Project settings, Apps, Attio.
On the Connect step, paste the key and select Next. Check that Connected to names the workspace you meant.
Work through Record type, Matching, Fields and Permissions, selecting Next on each.
On Placement, switch on at least one of Issue panel, Activity tab or Issue sidebar, then select Finish setup.
There is no Save button in the wizard. Next saves each step as you go, and the key is stored only if Attio accepts it with both read permissions.
#What happens next
Open an issue in the project. The card shows the matched Attio record in the places you chose. After setup the wizard becomes a row of tabs, so you can change one thing later without walking through the rest. See Check the Attio card appears on an issue.
#If it does not work
That key is the wrong length: an Attio workspace key is exactly 64 characters. Copy it again, whole.
The key works but is missing permissions: edit the same key in Attio to add the permissions named, then try again.
Attio rejected this key: it has usually been revoked or belongs to another workspace. Read the reason under the heading before replacing it.
Saved, but the card is not switched on yet: a site administrator needs to approve the app's new permissions in Admin Hub.
#Related
One key, one project, one card.
