Step 3: Choose how issues are matched
This is the step that turns an issue into a record. Exactly one of three methods runs. Two read the reporter's email address on the server; the third reads a Jira field on the issue instead, which is what a software or business project needs when the person raising the issue is a colleague rather than the customer.
#The three ways to match
Option | What the app sends to Attio | Typical record type |
|---|---|---|
Match the person | The reporter's whole email address | The object holding people |
Match their company | Only the part of the reporter's address after the @ | The object holding companies |
Match a field | The value of a Jira field on the issue, read as A name, A domain or An email address | Whichever object the field names: Companies for a company name or domain, People for a contact |
#Choosing the attribute
Once the record type is chosen, the app lists the attributes that could hold the value, labelled Attribute holding the email address, Attribute holding the domain or Attribute to compare the field against. Where Attio enforces an attribute as unique, the screen says so, which is a good sign you have picked the right one.
For Match a field, also choose the Jira field to read the customer from and say under What that field holds how to read it. A name is compared exactly against a text attribute; a domain, full URL or address in the field is reduced to its domain; an email address is compared the way a reporter's would be. See Link Jira issues to Attio records with a Jira field.
Domains are compared sensibly. Attio compares the registrable domain, so a reporter at mail.acme.co.uk still finds a company stored as acme.co.uk.
#Domains the project ignores
Matching a company by domain only makes sense for addresses that belong to a company. The app ships with a list of around 165 free-mail domains that are never looked up. Add your own under Domains this project ignores, and force one to match under Domains to match anyway. The same lists apply when a field is read as a domain.
#A few things worth knowing
Switching between the three options clears the record type, the attribute, the fields and the rest of setup, because none of it belongs to the new choice. The screen asks you to confirm first.
A text attribute is compared whole, so it only matches a record whose text is exactly the value. Attio's own domain attribute type is the more forgiving choice for domains.
A reporter with no email address on their Jira account cannot be matched by the first two options, and the card says so without naming them. Match a field needs no email address at all.
When matching by domain, more than three records sharing a domain are refused rather than guessed between.
#Related
A value in, a record out.
