Define "beautiful data" => Define ideal user stories for demo purposes

As per recent discussion in Test data Working group, we will need to identify what are the potential user stories that SAs would like to see demo'ed. This will help us identify the next set of data and plan accordingly.

This is related to !83656 (merged)

• Boards (epic & issue boards)
• Issues
  • Service Desk issues
  • Designs within issues
• Labels
• Environments
• Merge Requests
• Iterations
  • burnup/burndown
• Milestones
  • burnup/burndown
• Use Case 3
  • Pipelines
  • Jobs
  • Code Coverage
  • Avoid Vulns at this time given the movement from JSON → DB.
• Repository
• CI/CD variables
• Branches
• Vulnerabilities
• Licenses Found
• Security Policies (this is repository dependent)
• GitLab Settings
  • Need to be scenario based. Different development styles & innersourcing philosophies.
• Incidents, error tracking
• Audit Events / Compliance Violations, Compliance Frameworks
• Analytics? ← This would a big ask. Because we have 3 different ways to generate “analytics” pages.
  • ETL → Scheduling a job to calculate this info (DORA metrics) over time.
  • Operational Data → Calculated on-demand (this is easiest)
  • ClickhouseDB → ETL → GitLab DB.
• Geo

MVP for Working Group

• Boards (epic & issue boards)
• Issues
• Labels
• Iterations
  • burnup/burndown
• Milestones
  • burnup/burndown
• Repository
• Merge Requests