14.2 Planning for Manage::Access

14.2 Planning for Manage::Access

  • Board link: {REPLACE_WITH_BOARD_LINK}

Internal Milestone %14.1 Review & Discussion 🚀

Milestone: 2021-07-23 to 2021-08-22

Capacity

Please order by From date

Person From To
everyone 2021-07-16 2021-07-16
@mksionek 2021-07-23 2021-07-23
@peterhegman 2021-08-04 2021-08-09
@ogolowinski 2021-08-22 2021-08-24

Objectives

Themes

  • 🏎 Performance
  • 🔒 Security
  • 💼 GitLab.com Enterprise Readiness
  • 🔽 Workspace Settings Inheritance
  • 😍 Usability
  • 📈 Customer Requests
  • 🛠 Engineering Allocation
  • 🏃🏾‍♀️ Rapid Action
  • 🏆 OKR
  • 🐛 Bug
Title Weight Theme Assignee Priority
[Feature flag] Enable use_traversal_ids 1 🏃🏾‍♀️ @alexpooley
Linear queries for GroupDescendantsFinder 3 🏃🏾‍♀️ @alexpooley
Cleanup migration of Set traversal_ids for every namespace 1 🏃🏾‍♀️ @alexpooley
Remove namespace id partial index 1 🏃🏾‍♀️ @alexpooley
Specialized Worker for Group Transfer 3 🛠 @manojmj
Specialized Worker for Group Share Creation 3 🛠 @manojmj
Specialized Worker for Group Share Deletion 3 🛠 @manojmj
Specialized Worker for Group Share Update 3 🛠 @manojmj
Confidential - 🔒 ``
Confidential - 🔒 @dblessing
Intermittent failure in browser_ui/1_manage/group/group_ldap_sync_spec.rb - Manage LDAP Group sync user filter method has LDAP users synced ? 🐛
POC: Add member management as a deniable policy 3 📈 Med
API support for group access tokens 2 📈 Med
API Endpoint for SAML Group Sync 3 📈 Low
Add pronunciation to GitLab profile page 1 📈 @manojmj Low
Change dropdowns in Admin / General / Visibility and Access control to be radio buttons ~frontend frontend 3 😍 @peterhegman Low
Create a download for the Secret when creating an application in Admin / Applications frontend 3 🔒 @peterhegman Med
Display selected timezone on user's profile frontend 2 📈 @peterhegman Low
The Banner prompting users to check their account recovery settings causes confusion frontend 1 😍 @peterhegman Med

Research/Needs Weight 🕵🏻‍♂️

Access 14.2 Needs Weight/Research Issue (for 14.3 work or later)

Desgin 🎨

Defining Success

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!

Previous <= => Next

Edited by Orit Golowinski