> For the complete documentation index, see [llms.txt](https://good-alchemy.gitbook.io/fabric-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://good-alchemy.gitbook.io/fabric-documentation/guides/running-github-integrated-incident-responses.md).
# Fabric for incidents
An incident is a critical and urgent bug that needs a quick response.
**In an incident, time is critical.**
[Fabric](https://www.tryfabric.com/) can create an issue and spin up an [Issue Room](/fabric-documentation/reference/issue-rooms.md) in seconds for your team to collaborate in. The Issue Room becomes your command center, and helps your team close your incident as quickly as possible.
## Our customizable incident workflow
With Fabric's [Templates](https://docs.tryfabric.com/reference/templates), you can set up a workflow that adds labels, assignees, notifies the right people, and opens a war room ([Issue Room](https://docs.tryfabric.com/reference/issue-rooms))... all automatically.
While the incident is ongoing, Fabric will send Pull Request notifications to your Issue Room, so everyone can see the progress at a code level.
Lastly, when the issue gets closed out, Fabric will [archive the Issue Room, ](/fabric-documentation/reference/issue-rooms.md#auto-archiving-issue-rooms)and all the messages will have been backed up to the issue.
## Better incidents with Fabric
### Integrate closely with GitHub
When you run incident management on Fabric, every incident is a GitHub issue, and every message is an GitHub issue comment. This follows SRE best practices of having everything back up to the issue.
### Zero-click war room creation
Using our [π¨ Incident Template](/fabric-documentation/recommended-templates/setting-up-an-incident-workflow.md) or a custom one, you can tell Fabric to always spin up an Issue Room.
Fabric will create an Issue Room for each new issue created with this Template.
The created Issue Room gets attached to the issue. We preview the last comment.
### Keep up to date on PRs
Since your Issue Room is your command center, any updates on the issue in GitHub will send to that Slack channel.
If someone comments in GitHub, it'll notify the room.
Anyone looking at the issue in GitHub will see a link to the Issue Room at the top of the issue.
If someone comments in GitHub, it'll notify the room. They'll also see a link to the Room.
#### Linked Pull Requests
When a [connected Pull Request](https://docs.tryfabric.com/reference/issues#closing-on-pull-request-merge) is opened, closed, or merged, it'll notify the channel.
No need to DM the channel when a review is needed.
### Your timeline is built for you
Slack has second-level timestamping, so you'll be able to see exactly when certain things happened.
And, because everything is backed up to a GitHub issue, you'll see it there, too.
### No fuss
We know that when you're running an incident, time is critical.
We try to get you and your teammates into the Issue Room as soon as possible, without having you jump through any hoops.
## Set up your incident template
### 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.
This is your Fabric Dashboard.
### Go to your templates page
To get to your Templates Page, click on `Templates`.
This is your Templates page.
### Select the incident template
Let's customize our [incident template. ](/fabric-documentation/recommended-templates/setting-up-an-incident-workflow.md)Click `Create a template from example`.
Choose `π¨ Incident`.
Choose `Start with this one` on the `π¨ Incident` Template.
Here, you can customize all details of the `π¨ Incident` Template.
### Configure your template
Continue setting up your template with these details:
| Setting | Value |
| --------------------------------- | -------------------------------------------------------- |
| Name | π¨ Incident |
| Overview | Start an incident for a bug that needs a quick response. |
| Description | `- Whatβs going on?` |
| Repository | \ |
| Default labels | `bug`, `critical` |
| Default assignees | \ |
| Default project column | \ |
| Issue Feed | \ |
| Create Issue Rooms automatically? | β
|
| Issue Room Prefix | `#incident-` |
| Show label field? | β
|
| Show assignee field? | β
|
| Show milestone field? | β |
| Show project field? | β
|
β