How Fabric uses Fabric

Internally, we love dogfooding Fabric! We've created 1000s of real issues in multiple repositories, and collaborated on them using Issue Rooms.
Everything we work on has an issue, and an Issue Room.
An example of how we use Fabric to create issues for our GitBook docs, which are hosted on GitHub.

How we use Fabric

A channel for every issue

For every new issue, we have Fabric automatically create an Issue Room Slack channel.
We use Fabric's custom prefixes to organize Issue Rooms further.
Any conversation we have about something we're working on goes into the related Issue Room. When an engineer opens a Pull Request for an issue, Fabric will notify the connected Issue Room.
Many teammates use Slack's sidebar sections to organize their issues dynamically. For example, our product manager, Maneesha, organizes her issues by person, and clicks through the channels each morning to see what she can help unblock.
An Issue Room for a feature. There was some conversation, a PR merged, and the room archived.

A channel for every issue type

We use Fabric's templates feature to automatically route and label issues. Each Issue Feed has one or more connected templates, which makes it really fast to create and triage issues of a certain type.
Not everyone is in every Issue Feed, and we encourage muting Issue Feeds as needed.
We have an Issue Feed for every type of issue.

A channel for every teammate

We use People Feed channels as a kind of public TODO list for each person. It helps us reduce the number of DMs we're sending, and makes it easier to ask for reviews and feedback.
People Feeds aren't a Fabric feature, since they are just simple Slack channels, but they work really well with Issue Rooms. If you want to ask for a review of something that's in an Issue Room, just link to it.
Linking to Issue Rooms from elsewhere in Slack works really well.
We have a People Feed for every team member.