### Proposal 1. Change some of the verbiage around Linked Issues for the Incident Issue type (all changes are also captured in the designs below as well!): - Existing `Linked issues` text becomes `Linked incidents, issues & alerts` - When a user clicks on the `+` sign and expands the form, `The current issue` text changes to `The current incident`. - In the same expanded form, `the following issue(s)` becomes `the following incident(s) or issue(s)`. - An additional field is added for inputing alerts. This field is displayed by default, and can be hidden if `blocks` or `is blocked by` is selected in the form radio buttons. 2. Allow for Alerts to be linked in addition to related Incidents and Issues to the Incident Issue type. ### Designs | Default state | Adding related content | | ------ | ------ | | || _**Note: the related issue and related merge request widgets are currently being unboxed in !87886. We should plan on matching the styling of this new links widget to whatever work is done in that MR. [Here's](https://www.figma.com/file/cNfWMYHqi3Qnq4KMDcIQM5/Related-incidents%2Falerts-widget-gitlab-com%26356057?node-id=749%3A52352) how that might look, depending on how the design is finalized in that MR.**_ [Figma](https://www.figma.com/file/cNfWMYHqi3Qnq4KMDcIQM5/Related-incidents%2Falerts-widget-gitlab-com%26356057?node-id=749%3A54154) ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ * [Cameron (Compliance Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#cameron-compliance-manager) * [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager) * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) * [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst) * [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager) * [Alex (Security Operations Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#alex-security-operations-engineer) * [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test) * [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops) * [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#priyanka-platform-engineer) * [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst) * [Eddie (Content Editor)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#eddie-content-editor) --> * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### Metrics <!-- How are you going to track uage of this feature? Think about user behavior and their interaction with the product. What indicates someone is getting value from it? Create tracking issue using the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md --> Increase Monitor - SMAU, Unique users that interact with Alerts and Incidents AND Monitor - AMAU - Alerts Active Users ### Implementation - [x] Stop syncing alert & incident statuses entirely (or showing an alert's escalation policy on the incident page). - [x] Allow incident escalations on any incident, regardless of alerts. - [x] Swap issues to allow many associated alerts. (`has_one` -> `has_many`)