A company usually runs one Jira site with one Jira project per product. An organisation in LetThemBuild maps onto that: the organisation's Jira connection is the site, and each of its projects uses its own Jira project with the same key — BIK in Jira for BIK here.
Use the organization's ticket system
In Project settings → Tickets & Jira, a project inside an organisation can choose Use the organization's ticket system, the default for one made there. A team's own projects belong to the team's organisation too: each is offered the choice, and one that never chose a ticket system uses it. The team's ticket system is LetThemBuild, or Jira once the team has connected Jira; each of its projects then uses its own Jira project (Create Jira project), and keeps our numbers until it has one. General and your private projects keep LetThemBuild and are not offered it. Its tickets go wherever the organisation's go, with its create mode and status map: our numbers, or Jira — in the project's own Jira project, or the organisation's until it has one, which the card says beside Create Jira project BIK. Only discussions started after the choice get issues; a project that chose LetThemBuild or Jira keeps its choice.
Every project inside an organisation also uses the organisation's Jira connection, whatever it chose.
When an organisation was made for you
If the organisation had a Jira connection when your folders were converted, each new project was matched to the one Jira project on the site with its key or its name. Matched, it uses that Jira project and takes its key. Otherwise it uses the organisation's ticket system. Nothing is guessed, and no issue was made for a discussion already there.
Connect projects to Jira
Where to find it. The organisation's Project settings → Tickets & Jira, or its folder menu → Organize → Connect projects to Jira…, on every app.
The list shows the organisation and every project in it, with what each uses. For a project without a Jira project of its own:
- Pick an existing Jira project and press Connect — the same switch as Settings → Tickets → Switch existing projects….
- Or press Create Jira project BIK (also on the project's own card). It makes a Jira project with the project's key and name, led by whoever connected Jira, from a Kanban template, and connects it; one with that key already in Jira is linked instead. Creating needs a Jira admin; anyone else is told so. It is always a click.
A number, once given, never changes: new discussions take Jira's from the start, and older ones keep ours with the Jira key beside.
Company board in Jira
Make the company board makes two things in Jira, once: a saved filter covering every Jira project the organisation's projects use, and a Kanban board on it named "Organisation — all projects". Afterwards the button becomes Open company board ↗. When a project is connected to Jira or taken off it, the filter is updated so the board keeps covering all of them. Only the filter's and board's ids are kept here.
A board's columns map by status. Projects that share one workflow give a tidy board; projects with different workflows still show, but their statuses may need columns of their own in Jira's board settings.
If your Jira account may not make filters or boards, the button says so; ask your Jira admin to make it, or to give you that permission.
What is stored
The Jira projects each project uses, and the company board's filter and board ids. No Atlassian account ids, names or addresses: a new Jira project's lead is looked up at the moment it is made and passed straight to Jira.
Before these buttons work
Creating Jira projects and boards needs more Atlassian permissions. The server's owner adds manage:jira-configuration write:board-scope:jira-software read:board-scope:jira-software to the app in Atlassian's developer console, sets the same list as ATLASSIAN_EXTRA_SCOPES, and whoever connected Jira connects again. Until then the buttons say so, and the organisation's Jira project stands in.