Fabric for other issues
When you're creating an issue, you're making a lot of decisions.
What labels should I add? What repository should this be in? What details should I include? Where should I post it so the right people know about it? What project should I put this in?
When you're building a product, doing data entry like this can drain your creativity.
You and your team will create higher-quality issues, with more predictability, that get addressed faster, and don't drain your energy.
We're all about reducing the number of decisions you have to make when it comes to issue tracking.
We even decided which templates you should start with. One for bugs. One for incidents. One for feature improvements and requests, which are easier to track separately. And one for technical debt.
Follow the guide below to get set up.
To get to your Fabric dashboard, click
Fabric under Apps in your Slack sidebar.If you don't see
Fabric there, search for Fabric in your Slack search bar, and then click on the Home tab.Find Fabric in the Slack sidebar or search for it in the Fabric search bar.
This is your Fabric Dashboard.
To get to your Templates Page, click on
Templates.This is your Templates page.
You can create a template from scratch, but we recommended starting with one of ours.
Most users start with one of our recommended Templates.
Here are our recommended Templates:
Emoji | Name | Overview | Issue Room Prefix |
🐞 | Report a problem you ran into using the product. | #bug- | |
🚨 | Report an urgent bug that needs a quick response. | #incident- | |
⬆️ | Suggest an idea for a way to improve a feature. | #improvement- | |
💡 | Suggest an idea for a feature to implement. | #feature- | |
🏗 | Document work that needs to get done to enable new features. | #debt- |
If you're setting up your first Template, start with
🐞 Bug template.Choose "Start with this one" on the "🐞 Bug report" Template.
Here, you can customize all details of the "🐞 Bug report" Template.
Here are the Template settings you can configure:
Setting | Description | Required? |
Name | The name that issue creators will see when selecting a template. | Yes |
Overview | The template overview that issue creators will see when selecting a template. | Yes |
Description | The default text that will show in the body field once a template is selected. | Yes |
Repository | The GitHub repository to create issues in. | Yes |
Default labels | The labels Fabric will automatically apply to each new issue. | No |
Default assignees | The assignees Fabric will automatically add to each new issue. | No |
Default project column | The project column Fabric will send each new issue to. | No |
Issue Feed | The Slack channel that new issues will be sent to. | No |
Only show in certain Slack channels? | The Slack channels that will show this template. Leave blank for all Slack channels | No |
Create Issue Rooms automatically? | Whether or not to create an Issue Room for each new issue. | No |
Issue Room Prefix | Choose a prefix for your Issue Rooms for this Template. ex. choosing bug will create channels in the format #bug-1234--typo-on-homepage. | No |
Show label field? | Whether to show the label field in the issue message. | No |
Show assignee field? | Whether to show the assignees field in the issue message. | No |
Show milestone field? | Whether to show the milestone field in the issue message. | No |
Show project field? | Whether to show the project column field in the issue message. | No |
Last modified 6mo ago