Team

Use Link Jira account below and search by name — the lookup runs on your runner with your own Jira credential and fills in the account id for you. Most Jira Cloud sites hide email addresses, which also makes them unsearchable, so a name matches where an email won't (type an email anyway and we retry with the part before the @). If your Jira account can't browse users, or the runner is offline, paste the id by hand instead: it's the last part of a Jira profile URL, e.g. …/jira/people/5b10ac8d82e05b22cc7d4ef5. When a deploy is refused for an unlinked account, the account id is in the refusal comment on the ticket.

When someone hits Ask/Implement on the Board or creates a ticket from Compose, the Jira comment or ticket is posted with their own Atlassian identity — not the runner's service account. That needs their Jira API token on the runner machine, set by an admin with:

allwright jira user-add <their-ticketpilot-login-email>

It prompts for their Atlassian email and an API token (they create one at id.atlassian.com → Security → API tokens and read it out — the token is stored only on the runner, never here). Takes effect immediately, no restart. Until it's set, that person's Board/Compose actions are refused with these same instructions — nothing ever posts under somebody else's name. allwright jira user-list shows who's configured. The runner's own account (whoever is the runner credential) needs no extra setup.

GitHub is similar but optional: PRs normally open with the shared runner token, but allwright github user-add <their-ticketpilot-login-email> makes the PRs from runs they trigger author as their own GitHub account, and allwright github set <repoName> gives one repo a separately revocable token. The chips on each person below show their current status for both.