Linear and GitHub

Some customer emails need work outside the inbox: a bug for a developer, a task for the warehouse. With Linear or GitHub connected, anyone on your team can create an issue there from a conversation, and the conversation links to it afterwards.

Only owners can connect or disconnect an issue tracker. Everyone on the team can create issues.

Connecting Linear

1. In Linear, open Settings > Account > Security & access and create a personal API key:
   • Under Permissions, choose Read and Create issues.
   • Under Team access, choose the teams that issues go to.
2. In Airmailer, open Settings > Issue trackers and choose Connect Linear.
3. Paste the key and choose Connect Linear.

Airmailer checks the key with Linear before keeping it, stores it encrypted, and never shows it again. Settings shows the workspace and the account the key belongs to.

Connecting GitHub

1. In GitHub, open Settings > Developer settings > Personal access tokens > Fine-grained tokens and generate a new token:
   • Under Repository access, choose the repositories that issues go to.
   • Under Repository permissions, set Issues to Read and write.
2. In Airmailer, open Settings > Issue trackers and choose Connect GitHub.
3. Paste the token and choose Connect GitHub.

Airmailer checks the token with GitHub before keeping it, and refuses one that can't reach a repository with issues turned on.

Creating an issue

1. Open the conversation and choose Create issue.
2. With both trackers connected, choose Linear or GitHub.
3. Choose the team (Linear) or the repository (GitHub). The one your business used last is chosen already.
4. Check the title and the description, and change anything you like.
5. Choose Create issue in Linear or Create issue in GitHub.

The title starts as the conversation's subject. The description starts with the customer's latest email as a quote, without the earlier emails it quotes, their signature or any email address, followed by a link back to the conversation in Airmailer. Nothing is sent until the create button is chosen, and then exactly what the dialog shows.

The issue then appears under Issues in the conversation, with a link to it in Linear or GitHub.

Whose account creates the issues

Issues are created with the connected key, so Linear or GitHub shows the account the key belongs to as their creator, whoever on your team created them.

Disconnecting

Under Settings > Issue trackers, an owner chooses Disconnect Linear or Disconnect GitHub:

• The stored key is deleted from Airmailer.
• Issues already created stay in Linear or GitHub, and stay linked in their conversations.
• The key itself keeps working until it's deleted in Linear or GitHub.

A connection also goes when the person who connected it is removed from your team, and when a closed business is deleted.

Privacy

• Only the title and description shown in the dialog are sent.
• Customer email addresses are left out of the description it starts with.
• Deleting a conversation, or a customer's data, deletes its links in Airmailer. The issues stay in Linear or GitHub, to delete there.

Troubleshooting

• "Linear didn't accept this key" or "GitHub didn't accept this token": copy it again, whole, or create a new one.
• No team or repository to choose: the key or token has access to none. An owner can connect again with one that has.
• "The GitHub token can't create issues in …": in GitHub, give the token Issues: Read and write access to that repository.