[GDS] Beautiful Data Stretch Goals

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

We were able to draft an MVP of what would constitute "Beautiful Data" in Define "beautiful data" => Define ideal user st... (#373741 - closed).

The complete list was fairly exhaustive, but this would be idea to have a seed file that contains all of the following:

• 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