Add links to support on new status pages
Problem to solve
A public status page is an efficient way to communicate with stakeholders on incidents and outages that are impacting services they depend upon. These stakeholders may be executive leadership at the company internally or it's customers. If there are multiple incidents occurring at the same time, a list of on-going or recently closed incidents/outages provides stakeholders with a 30,000 ft view into the state of services with the option to drill down into particular problems.
Continuing the work started in #205164 (closed), this issue is meant to focus on adding the support link to the header of the pages in the new status site.
Intended users
Status page has two unique sets of intended users. The first group is response engineers using GitLab to manage incidents that want to provide incident status.
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
The second group is the vast array of stakeholders who want to consume the incident status. This can include everyone from business executives to customers.
Further details
This work supports the Status Page vision.
Proposal
Add the support link to the header of the new status pages, connecting users directly to assistance, if required.
Still TBC - whether the link should be to the general support page, or directly to the "submit a new request" page.
Design
| Support link on list page | Support link on detail page |
|---|---|
 |
 |
Technical details
TBD
Permissions and Security
Documentation
Documentation is required. We will need to create a brand new section in the GitLab docs and call it Status Page.
Availability & Testing
What does success look like, and how can we measure that?
Links / references
Full set of mocks for the entire workflow is on Sketch cloud
Full user flow is also visible on Mural