Part of the plan to improve the engineering efficiency of ~"group::optimize" is to have all group-owned features covered by seeds/fixtures. This epic joins all issues needed in order to have all features owned by Optimize group covered by a seed, fixture, or rake task. The issues were created based on the table below which was extracted from https://gitlab.com/gitlab-com/gitlab-OKRs/-/work_items/2697. | Feature | Fixture/Seed | Tasks | |---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Devops Adoption(Admin,Group,Project) | [31_devops_adoption.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/db/fixtures/development/31_devops_adoption.rb) | * Fix flaky errors, we should create a new project or accept a <br>GROUP_ID when running it.<br>* Output project URL when seed finishes | | Value Streams Dashboard(Group) | [17_cycle_analytics.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/fixtures/development/17_cycle_analytics.rb) | * Add deployment data<br>* Add vulnerability metrics<br>* Dora Metrics should be included after <br>gitlab-org/gitlab#377805 | | Value Stream Analytics(Project/Group) | [30_customizable_cycle_analytics.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/db/fixtures/development/30_customizable_cycle_analytics.rb) | * Create a custom value stream and assign stages to it<br>* Accept `PROJECT_ID` and if not present create a new project with group<br>* Fix MRs not getting merged | | CI/CD analytics(Project/Group) | No seed | * Use DORA metrics shared seed from <br>gitlab-org/gitlab!120358<br>* Add deployments<br>* Create multiple pipelines with different status | | Contributions Analytics(Group) | [90_productivity_analytics.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/db/fixtures/development/90_productivity_analytics.rb) | * Allow to accept an existing <br>PROJECT_ID<br> or create a new project<br>* Fix dates where issues and merge requests are created to match the chart range of 3 months<br>* Add different users creating commits/issues/merge requests | | Productivity analytics | [90_productivity_analytics.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/db/fixtures/development/90_productivity_analytics.rb) | * Merge some MRs with file changes | | Issue analytics(Group/Project) | `bin/rake "gitlab:seed:insights:issues[group-path/project-path]"` | Add following properties to rake task: <br><br>* Milestone<br>* Iteration<br>* Weight<br>* Due date<br>* Assignee | | Insights(Group/Project) | `bin/rake "gitlab:seed:insights:issues[group-path/project-path]"` | Include DORA metrics from shared seed after https://gitlab.com/gitlab-org/gitlab/-/merge_requests/120358 is merged. | | Repository analytics(Group/Project) | [14_pipelines](https://gitlab.com/gitlab-org/gitlab/-/blob/ad94ca3352f6129b8c8c31b2e04429dc8da5d820/db/fixtures/development/14_pipelines.rb) | We could fix[14_pipelines.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/fixtures/development/14_pipelines.rb) | | Code review | [90_productivity_analytics.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/db/fixtures/development/90_productivity_analytics.rb) | | | Merge Request analytics(Project) | [90_productivity_analytics.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/db/fixtures/development/90_productivity_analytics.rb) | Data should appear after some MRs gets merged on the seed as required for other charts.