Who can help with this incident?

Release notes

Problem to solve

During an incident, once you have identified what is causing the problem, the next step is to identify who can help

Intended users

The primary user during an incident is the incident responder to quickly identify who might know more that can help them.

User experience goal

Proposal

Further details

Tools like backstage.io and what some are discussing as a pajamas for infrastructure have a much bigger scope than what is described in this issue. We want something fairly straightforward. Something went wrong, we want to be able to identify (and perhaps page) who can help. So we don't necessarily care to be a single source of truth, but we want the information to be up to date so synchronization or a way to directly input and update the information is necessary.

Information that is housed in GitLab projects or groups can be a great starting point.

Permissions and Security

Documentation

Availability & Testing

Available Tier

Feature Usage Metrics

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

What is the type of buyer?

Is this a cross-stage feature?

What is the competitive advantage or differentiation for this feature?

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.