Fabric Documentation
Fabric lets your team create, collaborate on, and close GitHub Issues - without leaving Slack.

Create, collaborate, close

Fabric brings your issues into Slack.
  • Create your GitHub Issue in Slack with /issue, by reacting with the πŸ†• emoji on an message, or clicking on a message. Use a Template to save time and route your issue.
  • Edit the issue within Slack. All changes sync two-ways with GitHub.
  • Fabric can open an Issue Room for your issue. Collaborate with your whole team in real-time.
  • Receive notifications in your Issue Room when engineers open and merge Pull Requests.
  • When the Pull Request is merged, your issue gets closed and Fabric archives your Issue Room.
Create a GitHub issue quickly from a template and collaborate in the Issue Room.
To try Fabric, join our early access.​

How it works

  • ​Templates let your team quickly create and route issues.
  • ​Issue Rooms let your team collaborate on issues.
Get started with our recommended Templates:
This will create (with your permission), five Slack channels: #feed--bug-reports, #feed--incidents, #feed--feature-improvements, #feed--feature-requests, and #feed--technical-debt.
Issue created with Templates get automatically routed to the right channel.​
The Issue Feeds that Fabric will create (with your permission!).
For new issues, you can tell Fabric to automatically open an Issue Room. You can do this at the Team-level Settings (which we recommend- you can always toggle it off), or at the Template-level.
When Fabric opens Issue Rooms, it applies the prefix linked to that Template, ex. "#bug-".
Nervous about creating a lot of channels?
Channels scale really well in Slack.
With Slack channels, unless you've joined, you won't get notified about updates on a channel, and it won't show up in your sidebar. You can also mute any channel that you are a member of.
Channel search works pretty well, so you'll find yourself going to Slack to find your issue quickly.
Last modified 4d ago
Export as PDF
Copy link