Attio for Jira

An agent picking up a request can see who raised it, but not who they are: 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 reads the reporter's email address, finds the matching record in your Attio workspace, and shows the fields you chose, on the request itself. It is read-only in both directions: nothing is written back to Attio, and nothing is written to the issue.

#Before you start

What you need	Why
A Jira Service Management project	The card appears on service desk requests only, and only for agents
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, or companies matched by email domain

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.

#Everything under here

OverviewWhat Attio for Jira is, who it is for, and what it will and will not do.Get startedEverything a project administrator does the first time, in order, start to finish.Setting upOne page for each step of the setup wizard, and the settings tabs it becomes afterwards.On the issueWhat an agent sees: the three placements, the card, and every state it can be in.MatchingHow a reporter becomes an Attio record, and what happens when they do not.Fields and valuesChoosing what appears on the card, and how each kind of Attio value is shown.AdministrationWhere the settings live, who may change them, what a site administrator can see, and how long changes take.Permissions and privacyWho can see the card, what the app asks Jira for, and exactly what leaves Atlassian.ReferenceSettings, defaults, limits and the honest list of what the app does not do.TroubleshootingSymptoms first: what you are seeing, why it happens, and what to do about it.

Read by the people who answer the tickets.