Attio for Jira
Whoever picks up an issue can see who raised it, but not who the customer is: the account they are on, what they pay, who owns the relationship, whether they are in trouble already. That lives in the CRM, and going to look means leaving the ticket.
Attio for Jira puts the record on the issue. The app finds the matching record in your Attio workspace from the reporter's email address, its domain, or a Jira field that names the customer, and shows the fields you chose on the issue itself. It works on service management, software and business projects. It is read-only in both directions: nothing is written back to Attio, and nothing is written to the issue.
On a Jira Service Management project you can also publish chosen fields to customers, who then see their own record on their requests in the portal.
#Before you start
What you need | Why |
|---|---|
A Jira project of any type | The card works on any project. The customer portal panel needs a Jira Service Management project. |
Project administrator rights | The settings live in the project, not the site |
An Attio API key | Created in your Attio workspace, with read access to records and to object configuration |
A record type worth showing | People matched by email address, companies matched by email domain, or any object matched on a Jira field |
The connection belongs to one project. There is no site-wide key. Each project that needs the card is connected separately, which is what lets two teams use two different Attio workspaces.
#How-to guides and FAQ
#Everything under here
Read by the people who answer the tickets.
