Every discussion gets a key like LTB-12 and a place on a board. Not a separate tracker to keep in step: the conversation is the ticket.
The fields
Type (task, bug, feature), priority, assignee, labels, components and a release — set from the strip above the discussion or from Details, on any device. A description that nobody has written shows the first thing you asked, which is usually right.
The board
Four columns to start with — in progress, review, done, and your backlog. A discussion the room agrees on moves itself to review, because an agreed answer is something to look at. Drag a card to move it by hand. Edit columns renames, reorders, adds or removes them, and the board is the same on the web, the Mac and the phone; an added column says which of the four it acts as, so an agreed answer still finds review and a release still counts what is done.
Projects
A folder becomes a project when you give it a key. Its discussions get that key's numbers, it can carry its own components and releases, its own default lead and rounds, and its own base branch. A project's discussions work in the project's checkout without being told which one.
The rest
An issues list for filtering across everything, an inbox for what is assigned to you or mentions you (the help centre has more on those), comments teammates can leave in a transcript that the room never answers, and an activity trail on every ticket of every field that moved and who moved it.