<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=588435) </details> <!--IssueSummary end--> ## Proposal To help understand the general characteristics of cycle time we should be using a scatterplot instead of a line chart. The line chart could be useful in other ways to understand how trends change overtime. :tv: [YouTube video walkthrough](https://youtu.be/dEjV8d6xAm0) [{width=644 height=363}](https://youtu.be/dEjV8d6xAm0) Example: [group::code review value stream analytics](https://gitlab.com/gitlab-org/gitlab/-/value_stream_analytics?created_after=2025-11-05&created_before=2026-02-02&value_stream_id=2008257&stage_id=2038213&label_name[]=group%3A%3Acode%20review&sort=duration&direction=desc&page=1) | Line chart | Scatterplot | | ------ | ------ | | {width=900 height=457} | {width=900 height=505} | In the scatterplot: - X-axis is the date on which the merged event occurred - Y-axis is the duration of time in the code review cycle This data already exists from our value stream analytics. To help improve the different phases of the code review cycle, there is this issue https://gitlab.com/gitlab-org/gitlab/-/work_items/588409+ to capture last approval and other fields. This is all part of the work around measuring the code review cycle time https://gitlab.com/groups/gitlab-org/-/work_items/20403 ## Prototype https://cycle-time-chart-5a216a.gitlab.io/ 1. Displays JSON data that we currently use for the value stream analytics as a scatterplot 2. Merge requests that are outliers can be excluded by clicking exclude 3. You can load your own data by uploading a JSON file 4. Everything is in local storage.