Issue Rooms are heads-down spaces (Slack channels) where your team can collaborate on issues.
Each message in the Issue Room is synced to the issue as a comment, and vice versa.
When your issue is closed, we archive your Issue Room.
Creating Issue Rooms
You can create an Issue Room on any issue by clicking on the Create Issue Room 🛋 button on the issue message.
Click this button to create an Issue Room.
If your issue message is collapsed, you can see this button on the issue detail modal.
Click on the "..." and then "See details..." on the issue message.
Click "Create Issue Room" on the issue detail modal.
Fabric will create the Issue Room, attach it to the bottom of the issue message, and add a link to the top of the issue body in GitHub.
Fabric will add the link to the Issue Room to the issue.
Fabric will attach a link to the Issue Room to the original issue message.
Turn auto-creation on for every issue
You can tell Fabric to always create an Issue Room when a new issue is created, either from Slack or GitHub.
Turn auto-creation on per-template
You can tell Fabric to always create an Issue Room when a new issue is created at a template-level.
Collaborating in Issue Rooms
Easily Invite Others
You can edit all details of the issue from the Issue Room.
To invite more team members to your Issue Room, click Invite team members.
Messages and Threads
All messages in the Issue Room back up to the issue as comments, even threads. Messages can include files or images, which also get included in the comment.
Threaded Issue Room Messages
When you send a threaded message in an Issue Room, it will look like a classic reply in GitHub. The parent message will be quotes, and your reply will show below.
Threading in an Issue Room in Slack.
The messages get created as comments in a GitHub issue.
When you send an image in a message in an Issue Room, that will also get added to the comment. You can even add multiple images.
A message with an image in an Issue Room in Slack.
The message gets created as a comment in the GitHub issue, with the image.
If someone added a comment from GitHub, it gets sent to the Issue Room.
A comment from GitHub in an issue with an Issue Room connected.
The comment is sent to the Issue Room, so everyone stays on the same page.
Auto-archiving Issue Rooms
When your issue is closed, we automatically archive your Issue Room for you.
Brainstorm Out Loud
The great thing about Issue Rooms is that it gives you space for collaboration.
Instead of sending messages and distracting your team in #engineering, send them in the related Issue Room. Messages get backed up to the issue and anyone who is really interested can preview and join the channel.
There are only two people in this Room, but communicating progress helps build momentum.
Feel Free to Leave
Team members may enter a leave an Issue Room multiple times throughout its existence.
We encourage this because it helps everyone stay in control of what channels they're in. And some team members may only have input in one phase of the issue. Invite design in early, and QA in later.
A Room for Every Issue
When you turn on your Team setting to always create Issue Rooms for every issue, Fabric starts to feel magical.
Knowing you have a space to discuss every issue will reduce distractions and let your team collaborate more frequently.
Issue Room Commands
Here are the special commands you can use in Issue Rooms.
See all commands
Shows you this command with a list of Issue Room commands.
See Pull Requests
Shows you the Pull Requests associated with this issue.
Close the issue
Closes the issue and lets you archive the room.
Add to the body
Type the following to add text, images, or files to the description of your issue:
`add` Here are the docs: docs.tryfabric.com
Type `todo` and some text in your Issue Room to add a task.
Fabric adds the text to the end of your issue's description.
Type the following to add a task to the description of your issue:
`todo` Implement dark mode
Type the following to add a finished task to the description of your issue:
`done` Scope out feature
Assign the issue
type the following to assign yourself to your issue: