Most software teams run two tools side by side. The tracker holds the plan: issues, statuses, who owns what. The chat tool holds the conversation: questions, decisions, the quick "is this done yet?". The two are supposed to describe the same work. In practice they drift apart within a week.
This post is about why that happens, and what changes when issues and chat live in the same workspace.
The gap between the board and the conversation
Picture a normal afternoon. Someone asks in a channel whether the login bug is fixed. A teammate answers from memory. The issue in the tracker still says "In Progress". A third person reads the thread, assumes it is done, and closes a related ticket. Nobody did anything wrong. The tools simply never talked to each other.
The usual fix is discipline. Paste links. Update the ticket after every discussion. Set up a bot that posts status changes into a channel. These help, but they all depend on people remembering to do one more thing. Under pressure, the extra step is the first thing dropped.
The deeper problem is that the conversation is where decisions actually get made, and the tracker is where decisions are supposed to be recorded. If they are separate products, keeping them in sync is a job. If they are one product, it is not.
One channel per board
In Deckbell, every project has a linked channel, named after the project. It is created the first time it is needed, and anyone in the workspace can join it.
The useful part is what shows up in that channel without anyone doing anything:
- A new issue posts a card. The card shows the key, the title and the current status. When the issue moves across the board, the status on the card updates with it.
- The card's thread is the issue's activity. Status changes and assignments appear there as short lines, so the thread reads like a log of what happened.
- Comments and thread replies are the same thing. A comment on the issue appears as a reply in the card's thread. A reply in the thread becomes a comment on the issue. You answer wherever you happen to be reading, and both places stay complete.
That last point is the one that removes the sync job. There is no "remember to copy this to the ticket". The ticket and the thread are two views of the same record.
On the board itself, Chat in the header opens the channel in a panel beside the columns. You can move a card and talk about it at the same time. From the channel, Board jumps back the other way.
Keys that link, messages that become issues
Two small details do a lot of work here.
First, an issue key typed anywhere turns into a link. Write WEB-142 in a message, a thread or a comment, and it points at the issue. Only your workspace's keys are linked, so text like UTF-8 stays plain. The issue page returns the favour: its In chat section lists the thread in the board's channel and every message that mentions the key, in conversations you are part of.
Second, any message can become an issue. Hover over it, choose Create issue, pick a board, adjust the title and description, and it lands in the board's first to-do column. The issue's description links back to the conversation, and the message's thread gets a note saying which issue it became. The person who raised the problem in chat can see it turn into tracked work without leaving the thread.
Talk it through without leaving
Some things are faster to say than to type. In Deckbell, a huddle is a quick call inside a channel or direct message: audio by default, with video and screen sharing when you need them. There is no link to share and no meeting to schedule.
Huddles can be about something specific. Open a thread and choose Huddle in its header, and the huddle is named after the thread. On an issue's page, the headphones button starts a huddle about that issue in the board's channel, or joins the one already running. While it runs, a live bar across the top of the channel shows who is in it and what it is about, with a Join button.
So the path from "I have a question about this issue" to "we are on a call about it" is one click, and the call is labelled with the issue it belongs to.
What this looks like day to day
A few habits change once the two sides are connected.
People stop asking for status in chat, because the status is on the card in the channel, and it is current. Discussion about an issue happens in its thread, because that is where the card is, and the thread is also the comment history. Someone who reads the issue later gets the whole conversation, not a summary of it.
Agents fit the same pattern. Mention an agent in a card's thread and it picks up that issue. Its "On it" note and the pull request card appear in the thread, next to the human discussion. See AI agents for how runs work.
None of this requires a new process. It requires the tracker and the chat to be the same product, so that the record and the conversation cannot drift apart.
Try it
Create a project, open its board and choose Chat in the header. Create an issue and watch the card appear. Reply in the card's thread, then open the issue and read the comment. The Boards & chat together page covers every detail, and the Chat page covers channels, threads, files and huddles.