13.9 Planning for Compliance

Boards

Build Board - Build all the things!

Next Up Board - Collaboration time! 🔨 👖

Release Kickoff Video

https://youtu.be/RNZbWmv3Vq0

Capacity notes

Please update this section with planned PTO or other capacity notes 😄

Objectives & Themes

  • Compliance frameworks
  • Compliance pipelines
  • Require Jira tickets on MRs
  • Group-level MR approvals (Refinement and implementation)

Defining Success

The work we do should increase the number of projects with compliance framework 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
Status Issue Category Theme DRI / Thanks
[Backend] Add 'compliance pipeline configuration location' value to custom compliance framework labels Category:Compliance Management 📈 @asubramanian1
[Frontend] Add 'compliance pipeline configuration location' value to custom compliance frameworks form Category:Compliance Management 📈 @rob.hunt
Display Compliance Framework disabled field for Maintainers Category:Compliance Management 👣
Create service classes for project-level push rule actions Category:Compliance Management 📈 @tancnle
Add a project-level setting to require Jira association in Merge Requests (BE) Category:Compliance Management 📈 @mwoolf
Evaluate group-level compliance pipeline configuration Category:Compliance Management 📈 @asubramanian1
Create merge request approval settings vue app with store Category:Compliance Management 👁 @tancnle
Optional enforcement of SSH key expiration Category:Compliance Management 📈 @mwoolf
Add Prevent approval of merge requests by merge request author checkbox to group MR approvals Category:Compliance Management 📈
Convert admin/users view - migrate admin action confirmation modals UX FY21-Q4 👁 @jiaan
Audit events showing removed user when user is still in the project ~bug 👁 @mwoolf

Stretch Goal(s)

These should only be picked up if they have a %13.10 milestone and after checking with @mattgonzales

Next Up

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!
  • 🍺
Edited by Tan Le