An incident is a critical and urgent bug that needs a quick response.
In an incident, time is critical.
Fabric can create an issue and spin up an Issue Room 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, you can set up a workflow that adds labels, assignees, notifies the right people, and opens a war room (Issue Room)... 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, 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 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.