## Overview Scheduled Reports deliver proactive, timely and relevant information to decision-makers, saving time and effort. Adding Scheduled Reports will allow decision-makers to focus on analyzing insights rather than spending time looking for the right dashboard with the relevant data. Following this feedback [1](https://gitlab.com/gitlab-org/gitlab/-/issues/381787#note_1184245309 "Value Streams Dashboard (aka Exec Dashboard): Feedback Issue for the Beta"), [2](https://gitlab.com/gitlab-org/gitlab/-/issues/353651#note_1011316826 "Customer Executive Dashboards [formerly called Customizable analytics dashboard]"), [3](https://gitlab.com/gitlab-org/ux-research/-/issues/2929#note_1788684119). ### [JTBD & Persona](https://gitlab.com/groups/gitlab-org/-/epics/9317#jtbd-personas "Value Streams Dashboard (aka Executive Dashboard)") ### User experience goal The DevOps manager should be able to automate the process of pulling data requested by the Executive. - In the [VSD post release survey](https://gitlab.com/gitlab-org/ux-research/-/issues/2929#note_1788821357) - "Reports Generation" [was selected](https://gitlab.com/gitlab-org/ux-research/-/issues/2929#note_1788684119 "VSD - Post-release survey findings") as the most important customization to improve decision-making.   ## Iteration path: 1. Report Generation - Adding a utility script that collects the data from the GraphQL API and stores it in a markdown. This utility will be configured via the via [VSD config YAML file](https://docs.gitlab.com/ee/user/analytics/value_streams_dashboard.html#using-yaml-configuration) 2. Delivery Setting - Create a pipeline template (.yml configuration pipeline). Use inputs instead of global variables. In the MVC the template will include these steps: 1. Open a new issue. 2. Collect the most recent VSD metrics results. 3. Add the the results as [markdown table](https://gitlab.com/gitlab-org/gitlab/-/issues/383827#proposal) to the issue description. 4. Add labels and assignees. 3. Scheduling will be done [Build > Pipeline schedules](https://docs.gitlab.com/ee/ci/pipelines/schedules.html#add-a-pipeline-schedule). 4. Add the pipeline template to gitlba-org CI/CD catalog for ~Dogfooding. 5. Once ~"group::pipeline authoring" will finished the restructuring the CI components - convert the template to a component that will take an artifact from the report generation pipeline and open an new issue. ## Example | [Metrics comparison for GitLab.org group](https://gitlab.com/groups/gitlab-org/-/analytics/dashboards/value_streams_dashboard) ~"severity::2" ~customer | Month to date May 1 - May 4 | April Apr 1 - Apr 30 | March Mar 1 - Mar 31 | |--------------------------------------------------------------------------------------------------------------------------------|-----------------------------|----------------------|----------------------| | New issues | 585 {- -85.7% -} | 4101 {+ +2.2% +} | 4192 {+ +7.1% +} | | Deployment Frequency | 117.0/d {- -11.6% -} | 132.3/d {+ 0.99% +} | 131.0/d {+ 3.0% +} |