An error occurred while fetching the assigned iteration of the selected issue.
14.2 Planning for Compliance
Boards
- Build Board (%14.2 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 Event Organization
- FY22-Q3 OKR
Capacity notes
Milestone dates: 2021-07-22 -> 2021-08-22
- Everyone: Friends & Family day
🌞 2021-07-16 - Austin: Vacation
🌴 2021-07-22 → 2021-07-28 (Thursday - Wednesday) - Rob: Parental leave
👶 2021-08-09 - 2021-11-08 (May occur earlier and I might return earlier too😅 ) - Max: 3 days (2021-08-03 to 2021-08-05)
- Jiaan: 3 to 5 days while I move in from 2021-08-02
🏘 - Sam: 2021-07-22/23
- fill in
Objectives & Themes
- Any %14.1 carry-over
- fill in
-
Bugs past SLO(triage report, bug board)- fill in
- Other bugs
- 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.)
- Handle missing or empty gitlab-ci.yml files using compliance pipelines
- P1 Refinement issues
- Group-level MR Settings (8 pts) OKR
- Items taken from
"workflow::scheduling"/"workflow::ready for development" -
UX SUS issues
- Carry-over: Move placement of "Compliance Framework" setting to Settings->General after Badges (1pt)
- Next up: Clarify date range constraints in Audit Events (3pts)
Deferred
- Technical debt (to total weight of 6 points)
- Group-level MR Settings OKR
Consider moving to following iteration and/or moving to workflow::scheduling
%14.1 (consider moving to following iteration and/or moving to workflow::scheduling)
FromFrom this milestone (consider moving to following iteration and/or moving to workflow::scheduling)
- Audit events continuation (9 pts as of 2021-06-15)
- Add external status check usage to usage ping (2pts)
- Compliance dashboard
- Introduce concept of Merge Request Violation - gitlab-org/gitlab#327119 (closed)
- Violation by merge requests - gitlab-org/gitlab#299359 (closed)
- Add new audit events (target points?)
- Three from audit_eventsdata_change_deletion OKR
%14.2
FromUX goals
- Move protected branch and merge request approval rule proposal into workflowplanning breakdown
- Identify or add examples to docs where necessary
- Prep for category maturity scorecard testing
Defining Success
- Successful resolution of the local changes bug
- Group-level MR settings
- User-impacting issues (several listed above in the themes)
Community Contributions
- Audit events for MR settings (gitlab-org/gitlab#336211 (closed))
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 |
---|---|---|---|---|---|
Variable can be used on include.ref (gitlab-org/gitlab#219065 (closed)) |
Category:Compliance Management | theme | dri | gitlab-com/www-gitlab-com!86710 (merged) | |
Assign compliance framework via API (gitlab-org/gitlab#333249 (closed)) | Category:Compliance Management | theme | dri | gitlab-com/www-gitlab-com!86709 (merged) | |
Add membership CSV export to root group (gitlab-org/gitlab#287940 (closed)) | Category:Compliance Management | OKR | dri | gitlab-com/www-gitlab-com!86708 (merged) | |
Add the projects compliance framework label to the group-level projects list (gitlab-org/gitlab#296742 (closed)) | Category:Compliance Management | theme | @rob.hunt | gitlab-com/www-gitlab-com!85924 (merged) | |
status | issue | category | theme | dri | rp mr |
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