[UX] Create incident reports of a poorly performing cohorts

[formgeist]

Summary

Related to #263

As a user inspects the auto-generated reports that we present on the poorly performing cohorts and pages, there's a need to be able to create an incident or snapshot of that presented report of 30 days in order to compare the impact of future enhancements.

User flow

• As a user, I want to be able to save the auto-generated report of a given 30-day interval so I can review past reports with new data once enhancements and improvements have been made.
• As a user, I want to be able to see who generated the incident report and when.
• As a user, I want to be able to see all incidents created for all services and environments.
• As a user, I want to be able to write my own comments and notes for each incident.
• As a user, I want to be able to share this incident with my team.
• As a user, I want to be able to group incidents together for multiple services and environments for broader improvements and in order to collectively analyze reports and results.

Open questions

• How do we deal with Spaces? If a team creates incidents in one space (Web team) and the Operations team create reports in another, do they see the reports altogether across multiple spaces?
• How long do we keep opened reports? Should the user be able to resolve reports, and thereby archiving them? That means reports have a status of "open" and "closed/resolved".

Report schema

• Report created timestamp
• Report edited timestamp
• The absolute range for the report (now - 30 days)
• Service name
• Environment
• Notes
  • Individual comments and notes attached to the parent doc
• Tags?

[elasticmachine]

Pinging @elastic/observability-design (design)

[formgeist]

@drewpost When you have a moment, could take a look at the above definition of the incident? I also wonder if incident is the right term, perhaps a "snapshot" (although that also clashes with some other terminology in Kibana/Elastic).