Skip to content

Dedicated Incidents

Problem to solve

We've been utilizing issues as incidents but, we've discovered that issues aren't as flexible as we need them to be, and they don't surface the content that's required for quick resolution of incidents.

Intended users

User experience goal

Ensure that people responding to incidents have quick access to all relevant and related content so they can resolve the incident with as little context switching as possible.

Proposal

As part of #217044 (closed), we put together a sample vision mock for incidents. But, we also hope to align whatever we propose for incidents with the work being done &3354. So, the goal would be to modify this vision proposal to fit within the framework established as part of the extensible issues effort.

Designs

Tab 1 Tab 2 Tab 3 Tab 4 Tab 5
Incidents-1 Tab_2 Tab_3 Tab_4 Tab_5

Fuller set of explorations is visible in Figma. There is also a simple clickable prototype. In these links, there is more information about the more options menu, the publishing functionality, the updated new issue form and the interaction for adding related alerts/incidents.

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited by Amelia Bauerly