# Fabric Documentation {% hint style="warning" %} Fabric is closing its doors. Thanks everyone for your support πŸ’œ. [Read the announcement.](/fabric-documentation/company-update.md) {% endhint %} ## Issue tracking your team will actually use [Fabric](https://www.tryfabric.com/) is issue tracking your whole team will *actually* use. Teammates can create, comment, edit, and close GitHub issues, without leaving Slack. Our powerful templates integrate closely with your Slack channels and let you collect more details upfront, leading to higher-quality issues and happier engineers. > β€œWe love using Fabric! And it was a breeze to set up." - Matt, PM from Bottle.com ## What you can do ### Create, edit, and close your issue With Fabric, you can easily create GitHub issues in any of your GitHub organization's repositories. No need to screenshot messages or copy Slack message links. ![Create issues quickly with slash commands, emoji reactions, or message actions.](/files/sYgNb6Sv8L9EZ1g9H90G) ### Powerful templates for fewer clicks Templates make it easier for the whole team to create high-quality issues.\ \ Set default labels, assignees, and route to a project. You can even configure templates to only be available in certain channels or change the order they show up in. You can choose to send issues created from a template to a certain channel, or automatically generate [Issue Rooms.](/fabric-documentation/reference/issue-rooms.md) ![Create powerful workflows with Templates.](/files/xbstpLiMCHZ6jvmI6r4I) ### Fully-automated issue channels [Issue Rooms](/fabric-documentation/reference/issue-rooms.md) are a powerful way to get work done. They let you bring in all stakeholders in a dedicated channel, and messages sync to the issue.\ \ Issue Rooms have been shown to close issues twice as fast, and Fabric can create and archive them for you automatically. > β€œIssue Rooms has changed how we work dramatically." - Tyler Richie, CTO of SproutFi ![Fabric can generate Issue Rooms for you. Close issues faster with stakeholders.](/files/MuAb1ISBUJbtbH003qvE) ### Friendly for non-engineers Fabric is designed for your whole team to use. Teammates can use Fabric without even having a GitHub account. They can create issues, comment and edit them, and participate in Issue Rooms in Slack, and everything will get synced back to GitHub. > "Having a more real-time way to discuss and track issues has been long overdue." - Brandon Arvanaghi, CEO of Meow ### Scales with your team Fabric fixes a bottleneck in your engineering process: engineers and non-engineers creating and triaging issues. Because Fabric lives in Slack, it's much easier for marketing, sales, and customer success to file issues. With our workflows, you'll collect more information up front, leading to higher quality issues and fewer DM interruptions for engineers. ## Next steps {% embed url="" %} Create issues from scratch or by using templates. {% endembed %} Get started with our recommended Templates: [🐞 Bug Report](/fabric-documentation/recommended-templates/bug-report.md) [🚨 Incident](/fabric-documentation/recommended-templates/setting-up-an-incident-workflow.md) [⬆️ Feature Improvement](/fabric-documentation/recommended-templates/feature-improvement.md) [πŸ’‘ Feature Request](/fabric-documentation/recommended-templates/feature-request.md) [πŸ— Technical Debt](/fabric-documentation/recommended-templates/technical-debt.md) 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](/fabric-documentation/reference/templates.md) get automatically routed to the [right channel.](/fabric-documentation/reference/issue-feeds.md) ![The Issue Feeds that Fabric will create (with your permission!).](/files/-MhsXgNmLMOupAb3SpnR) For new issues, you can tell Fabric to automatically open an [Issue Room](/fabric-documentation/reference/issue-rooms.md). You can do this at the Team-level Settings (which we recommend- you can always toggle it off), or at the [Template](/fabric-documentation/reference/templates.md)-level. ![When Fabric opens Issue Rooms, it applies the prefix linked to that Template, ex. "#bug-".](/files/-MhsXwsnCWFo2bLYfDSX) 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. ![](/files/-MhsYX_wAuHxA485WWFK) {% content-ref url="/pages/-Mjjx07FdfcGF3-\_Ns5y" %} [Fabric for bugs](/fabric-documentation/guides/upgrade-your-bugs-channel.md) {% endcontent-ref %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://good-alchemy.gitbook.io/fabric-documentation/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.