14.7 Planning for Compliance

This issue and linked pages contain information related to upcoming products, features, and functionality. It is important to note that the information presented is for informational purposes only. Please do not rely on this information for purchasing or planning purposes. As with all projects, the items mentioned in this video and linked pages are subject to change or delay. The development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Once moved out of draft, update the kickoff issue

Table of Contents

Boards

Different boards we use for planning and organization

Capacity notes

Capacity by team member

  • @aregnery UX (4+ weekdays OOO)
    • 🎅 Christmas Eve | 2021-12-24
    • 🎆 New Years Eve | 2021-12-31
    • Tentatively planning to take a few more days
  • @djensen OOO from 2021-12-23 to 2021-01-03 (8 weekdays OOO)
  • @eread OOO from 2021-12-20 to 2022-01-10 (16 weekdays OOO)
  • @huzaifaiftikhar1 OOO on F&F days + 1 more (3 weekdays OOO)
  • @mwoolf OOO from 2021-12-23 to 2022-01-14 (15 weekdays OOO, leaving 25% capacity)
  • @sam.white OOO from 2021-12-23 through 2022-01-03 (8 weekdays OOO)
  • @jiaan OOO from 2021-12-23 to 2022-01-05 (10 weekdays)
  • @rob.hunt OOO from 2021-12-20 to 2022-01-03 (10 weekdays)

Objectives & Themes

  1. Any security & reliability issues that arise
  2. Bugs past SLO and other bugs (triage report, bug board)
  3. Project deletion
    1. Work on blocking issues for, and hopefully start on simplifying recovery of accidentally deleted projects on gitlab.com backend infradev
  4. Any %14.6 carry-over
    1. API-based Streaming Audit Events
    2. Convert compliance dashboard into an insightful report 4️⃣
      1. Introduce concept of merge request violation 5️⃣
      2. On MR merge, save a list of compliance violations that occurred at the point of merging 1️⃣
      3. Add GraphQL type to allow retrieval of compliance violations within a group 1️⃣
      4. Compliance report merge request violations frontend MVP
      5. Add a filtering feature to the compliance report 3️⃣
      6. Add sorting to table columns in the compliance report
  5. ~SUS issue list (stack ranked) | This milestone
  6. Progress on refinement queue (until 35 weight are in workflowready for development and workflowscheduling. This number is based on velocity for one milestone. Goal is to have one milestone worth of work refined. Check out the Next Up board to see how much is refined)
    1. fill in
    2. P1 Refinement issues
  7. frontend can pull in issues from the Pajamas OKR issue list if there's any available capacity remaining.
UX goals (stack ranked)
  1. ✔ Complete workflowdesign for #343577
  2. 🕵️ Setup environments for categories
  3. 📣 Send out recruiting for CMS evaluations
  4. ✏️ Refine designs for a deeper frontend backlog
  5. 🤝 Finish updating last two issues for global alerts in GitLab
  6. 📢 Consult as needed in cross-stage efforts
  7. 🚀 Pickup Community Contribution reviews

Deferred Items

Deferred items from previous and the current milestone

Consider moving to following iteration and/or moving to workflow::scheduling

From %14.6 (consider moving to following iteration and/or moving to workflow::scheduling)

From this milestone (consider moving to following iteration and/or moving to workflow::scheduling)

Release Post Items

Legend

  • 📈 - New feature focused on adding value to the end user
  • 👣 - Iterating on an existing feature to improve it or fix a bug
  • 👁 - Backstage improvements or tech debt work

Read more about how we prioritize issues and set status in the Handbook

Status Issue Category Theme DRI / Thanks Release Post MR
Improved Workflow for Recovering Deleted Projects
Convert compliance dashboard into an insightful report
Edited by Austin Regnery