Three kinds of folder sit in the sidebar. A project has its own ticket key and numbers, page, instructions, files, memory, components, releases, Jira settings and working folder. A plain folder groups discussions inside a project and belongs to it. An organisation is a top-level folder that holds projects: a company folder with one project per product, each its own repository.
A discussion belongs to the nearest project at or above the folder it sits in. A plain folder inside ChildCheck is part of ChildCheck; a discussion filed straight in the organisation belongs to the organisation, which keeps its own key.
Marks in the sidebar
An organisation shows an org badge. A project below the top shows its key beside its name (CHI). A top-level project looks as it always has. A plain folder shows nothing extra.
The Projects page
The Projects heading in the sidebar, or View All Projects under the tree, shows each project and organization as a card: description, last activity, key and discussion count. Search by name or description; sort by Recent Activity, Name or Date Created. ••• offers Open, Pin to Top, Project Settings and Archive. An archived project leaves the sidebar, keeps its discussions, and waits under Archived.
Making and unmaking projects
Where to find it. The folder's menu → Organize, on every app (Mac and web: right-click or •••; iPhone: long-press).
- Make it a project… on any plain folder. It asks for a key and suggests one that no other project of yours or your team's uses. The discussions under it are renumbered onto its own counter, oldest first.
- Stop being a project… on a project with no discussions numbered under it. It asks first. One that has discussions says how many; move them first, because a ticket's number is its name.
- Make each folder here a project… on a top-level folder: every plain folder directly inside becomes a project of it. It asks first.
All three live under Organize in the folder's menu. Project overview and Project settings… appear on every project, at any depth.
What a project takes from its organisation
Until a project sets its own, it uses the organisation's:
| Thing | How it applies |
|---|---|
| Jira connection only | Always the organisation's (the team's, for a team organisation) |
| Seats, leader, rounds for new discussions | The organisation's defaults until the project sets its own |
| Guardrails | The organisation's bound profile until the project binds one |
| Instructions | Both apply: the organisation's first, then the project's |
Project settings → General says Inherits from … for each. Team sharing and project members stay on the organisation; every project inside a shared organisation is shared with it.
One board for everything
Open Board from an organisation (its menu, or board on its page) and the board shows every project's tickets together, each card wearing its own key, with a chip per project to narrow to one. A project's own board shows only its tickets. The project filter on the board and in Issues lists organisations as "… — all its projects".
The move to organisations
When this arrived, each account was converted once: every folder directly inside a top-level folder that holds folders became a project, with a unique key from its name (ChildCheck → CHI, QuotePro Paint → QPP), its working folder where one was known, and its own counter. A top-level folder with nothing inside stayed as it was; folders deeper down stayed plain. Your inbox says what changed.
Renumbering and old keys
Discussions now inside a new project took its key with fresh numbers, in the order they were started: GPU-330 became BIK-1. The old key is kept for good. Search finds the discussion by either; a link, a branch name or a pull-request title that says GPU-330 still finds it; the key's tooltip says "was GPU-330"; the activity feed records the change. Moving a discussion into or out of a project with its own counter later does the same. Moving between projects that share the account's counter keeps the number, as before. Jira keys never change.