The card disappeared from every issue
The card was on every request this morning and now it is on none of them. If somebody used "Reset to defaults" on the Connection tab, that is exactly what it does, and the on-screen description says so before the second press.
There is no key-only disconnect. Removing the key and keeping the setup is not an option the app offers.
#What Reset to defaults removes
The description on the button reads: "Removes the API key, the record type, the matching attribute, every field on the card, the linked record settings, the audience and the placements, and clears everything this app has cached about your Attio records. The card comes off every issue in this project and setup starts again from the beginning. Nothing in Attio itself is changed or deleted."
It takes two presses. The first reveals a confirmation with "Yes, erase this project's Attio setup" and "Keep my settings", and nothing is removed until the second.
#What it does not touch
Nothing in the Attio workspace. No record, object or key is changed there, so a key you no longer want has to be revoked in Attio separately.
Facts about Jira rather than Attio: who reports a request, whether a viewer can read a request, a person's Jira group membership, and a person's display name and picture. None of them carries CRM data and each is re-read from Jira on its own schedule.
Because the reset also clears the records the app had cached for that project, a project that reconnects to a different Attio workspace cannot be served the previous workspace's customer data.
Pasting the key back does not switch the card on again. The placements went with the reset, so connecting again leaves the card showing nowhere until an administrator chooses a placement. This is deliberate: nobody should find customer data reappearing on live requests without somebody saying so. Once the key is gone the settings page also goes back to the six-step wizard, starting at Connect.
#Other reasons a card can vanish without a reset
What happened | What you see |
|---|---|
Every placement was switched off | The card comes off issues at once. The settings page reads "The card is not shown anywhere yet. Choose a placement to switch it on." |
The record type was changed | Changing the object clears the fields chosen under it, and a project with no chosen fields cannot resolve a card, so it comes off issues until the fields are chosen again. |
The key was revoked in Attio | The card does not disappear. It shows "The Attio connection for this project needs attention." instead. |
The viewer lost a permission or left a restricted group | It vanishes for that person only, within about fifteen minutes, and for nobody else. |
Jira refused the project update | The card never appeared in the first place, and the settings page says so under "Saved, but the card is not switched on yet". |
#The site-wide list follows the key
A project appears on the site administrator's list of connections as soon as an Attio key has been stored for it, even if setup is unfinished, and it drops off when the key is removed. That list can be up to about half a minute behind a change made a moment earlier, so a project that has been reset may linger briefly.
#A few things worth knowing
Reset is the only way to remove a key, and it removes everything else with it. Saving other settings never clears the stored key, and leaving the key field empty means "keep the key this project already has".
Nothing in Attio is changed by a reset, so an unwanted key stays live in the CRM until somebody revokes it there.
A project reappears on the site-wide connections list as soon as a key is stored again, before any placement has been chosen, so being listed there is not a sign the card is showing anywhere.
#Related
There is no key-only disconnect. There never was.
