Every discussion is a ticket. By default it wears our number — DDP-12 from its project's key — on our board, with nothing to connect. A project can use a Jira Cloud project's keys instead: its discussions get real Jira issues, wear their keys (PLAT-1043) everywhere ours showed, and the card and the issue's status follow each other.
Connect Jira once
Where to find it. Web: Settings → Tickets → Connect Jira, or Connect for the team for a team's owner or admin. Atlassian asks you to grant access to one Jira Cloud site. The Mac and the iPhone use it through your account and never hold a Jira token. Disconnect removes our webhooks and forgets the tokens; to end the grant, remove the app from your Atlassian profile.
The same page sets Ticket numbers for new projects, LetThemBuild unless you choose Jira. The Mac and the iPhone have the same Settings → Tickets choice, naming the connected site; connecting stays on the web.
Pick Jira for a project
How to use it.
- In Project settings → Tickets & Jira, choose Jira. It asks first; every change there saves at once.
- Pick the Jira project, for example Platform (PLAT).
- Choose Create a Jira issue for discussions that already have our number: When it lands on the board (the default), For every discussion or Only when I ask (Create Jira issue on the ticket strip).
- Check Status mapping: each board column and the Jira status it means, both ways. A Jira status nobody mapped lands by its kind: to do in the backlog, in progress in progress, done in done.
- Post final answers and PR links to Jira posts the agreed answer and pull request to the issue, once per answer.
- Leave Sync the assignee with Jira on to keep the assignee in step both ways. Whoever connected Jira is always found; others are matched by email. If you use a different address in Jira, set My Jira email in Settings → Tickets on any app. Someone Jira can't find is left as is; whoever assigned them is told in their inbox. No Jira account details are stored.
One number, given once
A new discussion in a project on Jira, with Jira connected, takes Jira's number: none until its first message, then its issue's (PLAT-1043). If Jira can't be reached then, it takes ours for good, the Jira key beside it once the issue exists. A discussion that already had our number keeps it when it gets an issue, the key linked beside it. An empty discussion never gets an issue. A team's projects can also Use the organization's ticket system.
Switch existing projects
Changing Ticket numbers for new projects to Jira leaves existing projects alone. Settings → Tickets → Switch existing projects… moves the ones you tick (team projects only if you can edit them) to one Jira project or one each. Their discussions keep their numbers; tick Make Jira issues for them too and each also gets an issue, its key beside its number.
Link an existing issue
On a discussion's ticket strip, Link Jira issue takes a key (PLAT-1043) or a link. The key is shown beside the discussion's number, and its card takes the issue's status.
When Jira is down
The issue is made when Jira answers. Status changes arrive by webhook, or within two minutes. Problems come to your inbox. Choosing LetThemBuild again keeps every linked key in step.
Assign work to LetThemBuild in Jira
A Jira admin installs the LetThemBuild app and links the site to your team (Jira settings → Apps → LetThemBuild → Configure). Each person links their own account once, from their Jira profile → Personal settings → LetThemBuild. Then assign a work item to LetThemBuild, mention it, or start it from an automation rule: the room works it in a discussion wearing the item's key, and Jira shows the answer and any pull request for you to post. Settings → Tickets has Let Jira assign work to LetThemBuild (on) and Run Jira tasks on my Mac (off).
Limits
Jira Cloud only. One Jira site per connection.