Release view that shows what MRs/issues/epics were in that release
Problem to solve
Teams need to know what is contained in a specific version of code, both before deploying that code, and for forensic analysis after deployment.
Further details
When looking at a release of code, a team wants to know what exactly is in that release before deploying it. While a code diff is helpful, seeing this information at a higher level can be easier to digest. e.g. what merge requests, issues, and epics are included in that release (that weren't included in the previous release).
Proposal
What does success look like, and how can we measure that?
(If no way to measure success, link to an issue that will implement a way to measure this)