Map people to their accounts

Say who your people are on a code host or a tracker, so work lands on the right person.

In short

A manager says who each person is on a connection. A tracker's assignee then lands on the right person even when the emails differ, and a pull request by someone mapped counts as your team's own.

Before you start

• Who: someone who may manage the organization's connections. People cannot map themselves, so nobody can claim another person's work.
• Works on: code hosts and work trackers.

Map one person

1. Open your organization, then Settings › "Connections".
2. On the connection, press "People", then "Map a person".
3. Choose the person and type their account: their login on a code host. On a tracker, their account id in Jira, their member id in Linear, their login in GitHub Issues, or their email where the tracker shows it. Jira Cloud often hides emails, so an account id is the sure way there.
4. Press "Save".

Import a list

1. On "People", press "Import a list".
2. Paste one person a line: their email here, their account, and optionally the name it shows there. You can paste from a spreadsheet.
3. Press "Map". Lines that cannot be mapped are left out and listed with why, so you only need to fix those.

What it changes

• Tracker sync: an assignee mapped here goes to that person, and back again as the account you mapped, even when the tracker hides their email.
• Code hosts: a pull request by a mapped person is not counted against the limit on outside authors.
• Nobody is ever matched by a name that merely looks alike. Someone who leaves the organization is taken off.