13.4 Planning for Compliance

Boards

Build Board - Build all the things!

Next Up Board - Collaboration time! 🔨 👖

Capacity notes

• Max OOO 2020-08-25; 2020-08-31 to 2020-09-06 (5 work days)
• Tan OOO 2020-08-27 - 2020-08-28 (2 work days)
• Aish OOO 2020-09-07 - 2020-09-11 (5 work days)
• Rob OOO 2020-08-31 (1 work day)
• Jiaan OOO 2020-08-28 (1 work day)

Objectives

• Continue implementation of product performance indicator instrumentation to track product usage and adoption for groupcompliance
• Iterate on ~"Category:Audit Reports" to work towards viable maturity state

Defining Success

These features should increase the number of compliance actions taken by customers.

Product Performance Indicator

• Manage:Compliance PPI - Add audit event searches to Usage Ping
• Manage:Compliance | PPI | Unique users of audit events API

Category:Compliance Management

• Add Revoke buttons to the PAT tab of the credential inventory 🚧 @rob.hunt 🚧
  • Add to the instance-level credentials inventory 🎉
    • Update documentation 🎉
  • Add to the group-level credentials inventory ⛔
    • Blocked by missing support in revoke service for managed groups
• Group Push rules API (Thanks @asubramanian1! 🎊)
  • 🚀 gitlab-org/gitlab!39642 (merged)
  • 🚀 gitlab-org/gitlab!39760 (merged)
  • 🚀 gitlab-org/gitlab!40136 (merged)
  • 🚀 gitlab-org/gitlab!40293 (merged)
  • 🚀 gitlab-org/gitlab!40658 (merged)

~"Category:Audit Reports"

Category:Audit Events

• Audit log does not show 2-factor failed logins
• Export audit events data to CSV
• Drop updated_at column on audit_events

~bug

Slipped from 13.3

Stretch Goal(s)

These should only be picked up if they're scheduled for %13.5 or after checking with @mattgonzales

• Export merge requests to CSV like already possible for issues
• Show total group and project count for users in admin users table
• Add Delete buttons to the SSH tab of the credential inventory
• Replace the delete SSH confirmation dialog with a Pajamas Modal

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

To-Do

• Define an approximate scope for the coming release.
• Apply appropriate labels to issues:
  • Priority
  • Department
  • Pricing Tier
• Review the proposed scope with Engineering.
• Review design objectives with UX.
• Get feedback and estimates from Engineering, confirming scope for the release.
• Final verification of issues scheduled for the release.
• Present selected issues in the Manage Kickoff on the 17th!
• 🍺