14.6 Optimize planning issue
%14.6 Planning for groupoptimize
%14.6 Milestone: 2021-11-18 to 2021-12-17
Capacity
Family & friends day: November, 29th
Please order by From date
| Person | From | To | Notes |
|---|---|---|---|
| Everyone (Family and Friends day) | 2021-11-29 | 2021-11-29 | |
| @blabuschagne | - | - | 5 days (~75% capacity for the milestone) |
| @djensen | 2021-11-23 | 2021-11-30 | 6 days (~75% capacity for the milestone) |
| @ahegyi | - | - | 1 or 2 days, not sure when |
Objectives
- Continue work on security issue burndown (Access burndown, followed by Dev burndown)
- VSA backend date range rebuild
- VSA usability improvements that don't require BE support
- Feature work on our high usage areas
- Contribute to a larger frontend effort
Themes
-
🏎 Performance -
🔒 Security -
😍 Usability -
📈 Customer Requests -
🏆 OKR -
🐛 Bug
| Title | Link | Weight | Theme | Priority |
|---|---|---|---|---|
| Developer Create and Delete options should remain visible in VS dropdown | gitlab-org/gitlab#327738 (closed) | 1 | ||
| VSA Exclude stages a user does not have permissions for | gitlab-org/gitlab#335810 (closed) | 5 | ||
| CI/CD Analytics: Usage metrics by tab | gitlab-org/gitlab#342926 (closed) | 2 | ||
| Resolve EE / CE difference of Group Navbar "Analytics" Menu Item | gitlab-org/gitlab#343840 (closed) | 1 | ||
| Move Value stream to top-level in analytics section of left sidebar nav | gitlab-org/gitlab#342373 (closed) | 1 |
|
|
| Tabs > HAML > Migrate app/views/snippets/_snippets_scope_menu.html.haml to GlTabs | gitlab-org/gitlab#230762 (closed) | 3 | ||
| Replace confirm danger modal in edit project form | gitlab-org/gitlab#345126 (closed) | 2 | ||
| Replace confirm danger modal in remove project fork form | gitlab-org/gitlab#345124 (closed) | 2 | ||
| Replace confirm danger modal in SSO authorize form | gitlab-org/gitlab#345127 (closed) | 3 | ||
| CI/CD Analytics: Tabs not visible to admin | gitlab-org/gitlab#343661 (closed) | 1 |
Research/Needs Weight 🕵🏻 ♂️
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 Adam Hegyi