# Fabric for other issues ## Create better issues, faster **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. With [Fabric](https://www.tryfabric.com/), just choose what [template](https://good-alchemy.gitbook.io/fabric-documentation/reference/templates) you want to use, and **the rest of the decisions are made for you.** **You and your team will create higher-quality issues, with more predictability, that get addressed faster, and don't drain your energy.** ## **How do I get started?** 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](https://good-alchemy.gitbook.io/fabric-documentation/recommended-templates/bug-report). One for [incidents](https://good-alchemy.gitbook.io/fabric-documentation/recommended-templates/setting-up-an-incident-workflow). One for [feature improvements](https://good-alchemy.gitbook.io/fabric-documentation/recommended-templates/feature-improvement) and [requests](https://good-alchemy.gitbook.io/fabric-documentation/recommended-templates/feature-request), which are easier to track separately. And one for [technical debt.](https://good-alchemy.gitbook.io/fabric-documentation/recommended-templates/technical-debt) **Follow the guide below to get set up.** ## Go to your Fabric dashboard 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.](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/7W03s3tZ7rjcSWVWZujm/Screen%20Shot%202021-08-23%20at%204.30.14%20PM.png) ![This is your Fabric Dashboard.](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/CftPugJqeHSGLIBYl2bc/Screen%20Shot%202021-08-23%20at%204.30.21%20PM.png) ## Go to your templates page To get to your Templates Page, click on `Templates`. ![This is your Templates page.](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/0aTCEZ7jNqyvWYh5qJDM/Screen%20Shot%202021-08-23%20at%204.35.02%20PM.png) ## Use a recommended template You can create a template from scratch, but we recommended starting with one of ours. ![Most users start with one of our recommended Templates. ](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/2Ji7XFIlLJ9JuiZ1SCHI/Screen%20Shot%202021-08-23%20at%204.37.43%20PM.png) Here are our recommended Templates: | Emoji | Name | Overview | Issue Room Prefix | | ----- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ----------------- | | 🐞 | [Bug template](https://good-alchemy.gitbook.io/fabric-documentation/recommended-templates/bug-report) | Report a problem you ran into using the product. | `#bug-` | | 🚨 | [Incident](https://good-alchemy.gitbook.io/fabric-documentation/recommended-templates/setting-up-an-incident-workflow) | Report an urgent bug that needs a quick response. | `#incident-` | | ⬆️ | [Feature improvement](https://good-alchemy.gitbook.io/fabric-documentation/recommended-templates/feature-improvement) | Suggest an idea for a way to improve a feature. | `#improvement-` | | 💡 | [Feature request](https://good-alchemy.gitbook.io/fabric-documentation/recommended-templates/feature-request) | Suggest an idea for a feature to implement. | `#feature-` | | 🏗 | [Technical debt](https://good-alchemy.gitbook.io/fabric-documentation/recommended-templates/technical-debt) | 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.](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/RLQYSrRsVaavRaxmDWot/CleanShot%202021-08-23%20at%2017.11.31@2x.png) ![Here, you can customize all details of the "🐞 Bug report" Template.](https://content.gitbook.com/content/D1GCmv3PztplZI6PqlYq/blobs/2rAb9sjKqd1PBoWDg1Jc/CleanShot%202021-08-23%20at%2017.14.10@2x.png) 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 |