14.1 Planning for Compliance
Boards
- Build Board (%14.1 milestone issues to be built)
- Next Up Board (all Next Up issues with workflow states)
- Refinement Queue (stack rank of issues to refine in order)
- Bug Board (bugs organized by severity labels)
- UX Board
- Audit Events Organization
Capacity notes
Milestone dates: 2021-06-22 -> 2021-07-22
- Everyone: Friends & Family day 2021-06-25
🌞 - Jiaan: OOO for ~14 days in total while I relocate from
🇿🇦 to🇳🇱 . 2021-06-16 -> 2021-06-24, and then another ~5 days in July. - Max: 2021-06-18 (1 day for a charity marathon hike.
😰 ) & 2021-06-26 - 2021-06-28 (2 days, for an actual holiday🌴 ) - Austin
- 2012-06-24 (Thu)
🌴 - 2021-07-02 (Fri)
🎡
- 2012-06-24 (Thu)
- Sam: At least one day around July 4
- fill in
Objectives & Themes
-
Any %14.0 carry-over
-
Other bugs
-
Technical debt if needed (to total weight of 6 points)
-
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.)
- Webhook-based audit events
- UX & frontend collab?
-
Technical Exploration for webhook-based audit events (overall epic)
- Max had created some child epics for this with both BE & FE component
- P1 Refinement issues
- Webhook-based audit events
-
Audit event OKR (7 pts as of 2021-06-15)
-
UX SUS issue
Deferred (consider moving to following iteration and/or moving to workflow::scheduling)
-
Bugs past SLO(triage report, bug board)- Not pursuing Deleted Projects not being properly deleted, because it should be resolved through another group's work.
- Technical debt
-
Group-level MR Settings
- gitlab-org/gitlab#332549 (closed)
- gitlab-org/gitlab#332548 (closed)
- gitlab-org/gitlab#325279 (closed)
- gitlab-org/gitlab#325620 (closed)
- Do we have/need additional frontend issues in the epic?
- Fill in
- Audit events continuation (9 pts as of 2021-06-15)
-
Compliance dashboardIntroduce concept of Merge Request Violation - gitlab-org/gitlab#327119 (closed)Violation by merge requests - gitlab-org/gitlab#299359 (closed)
UX goals (stack ranked)
-
✔ ️ Run competitor evaluation and share insights -
✔ ️ Solicit feedback on blunt🔨 protected branches & MR Approval Rules -
✔ ️ Have quick wins with"group::pipeline authoring"/"group::pipeline execution" scheduled -
✔ ️ Audit Event Webhook design ideation -
⏭ Identify or add examples to docs where necessary
Defining Success
The work we do should address high-priority customer needs, driving Other GMAU
as well as increase our paid GMAU
, viewing compliance features
Community Contributions
Deliverables
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 |
---|---|---|---|---|---|
gitlab-org&4637 (JIRA integration) | Category:Compliance Management | gitlab-com/www-gitlab-com!83792 (merged) | |||
gitlab-org&3869 (External status checks) | Category:Compliance Management | gitlab-com/www-gitlab-com!84079 (merged) | |||
gitlab-org/gitlab#329362 (closed) (Compliance framework audit event) | Category:Audit Events | gitlab-com/www-gitlab-com!85074 (merged) | |||
gitlab-org/gitlab#220127 (closed) (SSH & GPG key via API audit event) | Category:Audit Events | gitlab-com/www-gitlab-com!85151 (merged) | |||
gitlab-org/gitlab#323905 (closed) (Instance admin audit event) | Category:Audit Events | gitlab-com/www-gitlab-com!85159 (merged) | |||
gitlab-org/gitlab#334682 (closed) (Compliance report drawer) | Category:Compliance Management | gitlab-com/www-gitlab-com!86199 (merged) |
Stretch Goal(s)
Next Up
- priority1 Next Up Issues -> Issues Analytics View
- priority2 Next Up Issues -> Issues Analytics View
- priority3 Next Up Issues -> Issues Analytics View
- priority4 Next Up Issues -> Issues Analytics View
Edited by Sam Kerr