### Problem to solve GitLab Incident issue descriptions support a rich set of display capabilities including images and embedded charts. If customers, users, and stakeholders don't have access to these visuals they lack meaningful context that can help them make decisions about how they will handle outages and performance degradations. Sharing visuals along with text raises the level of transparency which breeds additional trust and confidence. ### Intended users See https://gitlab.com/gitlab-org/gitlab/issues/205164#intended-users ### Further details This work supports the [Status Page vision](https://about.gitlab.com/direction/monitor/debugging_and_health/status_page/). <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal * Images added to incident issue descriptions should be rendered along with text on the accompanying status detail page automatically as part of the description creation/update process. #### Out of scope * Rendering charts on status detail pages. (User will need to screen cap charts and paste them in as images in order for them to show up on the status page.) * Posting comments to the detail page. (Images from the issue description only) ### Design As a follow-up to the work completed in https://gitlab.com/gitlab-org/gitlab/issues/205165, this work will allow us to pull images (jpg and pngs) from the issue description and add them to the incident detail page. Here is how that could look, if we use the example of a screengrab of a chart:  ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> ### Documentation Documentation required. Please add changes to a new section called Status Page. <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> A new end to end test will be introduced to cover the functionality of this feature, please follow up in [E2E test for Status Page with Incidents](https://gitlab.com/gitlab-org/quality/testcases/issues/264) ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Links / references [Measure spec](https://gitlab-org.gitlab.io/gitlab-design/hosted/amelia/gl%2335430-status-page-mvc-spec-previews/) Full designs for the MVC and future iterations in [Sketch cloud](https://sketch.cloud/s/z3yZb) [User flow](https://app.mural.co/t/gitlab2474/m/gitlab2474/1580410553179/f5d39aff6b11055ffbe968da4094e21c6710741f) viewable in Mural