Coverage for Nick Leonard from 2023-05-29 until 2023-09-19
Intent
Coverage for parental leave
Anticipated due date is currently Friday, June 9
@esybrant
will cover Project Management in my absence
🤝 Responsibilities
Priority | Responsibility | Link | Primary backup DRI | Secondary backup DRI |
---|---|---|---|---|
HIGH |
Planning objects high level IA (KR3) | gitlab#411841 (closed) | @nickbrandt |
@esybrant, @jackib |
HIGH |
Planning objects detail design (KR2) | gitlab#410068 | @nickbrandt |
@esybrant, @jackib |
HIGH |
Work items attributes/a11y design and coordination with Foundations | (currently part of KR2) | @nickbrandt |
@jackib |
HIGH |
All other work items inquiries | @esybrant, @gweaver |
@nickbrandt, @jackib |
|
MEDIUM |
Reviewing Community Contribution merge requests | MRs | @esybrant |
@nickbrandt |
LOW |
Pair designer support (@nickbrandt through Q2) |
ADD LINK |
@esybrant |
💪 Coverage Tasks
Include specific issue links for tasks to be completed by your backups.
Potential needs
Item | Needs | Notes | Assignee |
---|---|---|---|
Add UI to set time estimate on issues and MRs (gitlab!113037 - merged) | UX review/approval | Limited existing design, but we've discussed this in the past and suggested an approach similar to what's shown (action + modal), which is also what's used for time spent. | @nickbrandt |
https://gitlab.com/gitlab-org/gitlab/-/issues/381879+ | Decision on rollup behavior OR filter behavior | This was design complete including customer validation, but addition of OKRs to milestones made this approach less clear. More in thread. | tbd |
FYI/No known needs
Item | Needs | Notes |
---|---|---|
Filter issues by due date (gitlab#19787) | Questions/issues | Should be built on existing patterns. Needs design for a more complete vision but not blocking MVC. Some early exploration in Figma. |
Convert a regular comment into an internal note (gitlab#365295) | Design | This was brought up while implementing work item internal notes, and has come up from dogfooding users recently as well. There is a basic proposal in the issue that I think could work pretty well but I haven't fully investigated yet. Should be issues+work items. |
Using `or` in issue/mr/epic list views and boards (&9260) | Review/support | Current OR filter is behind a FF (default off) as it is difficult to use; was implemented as an MVC given challenges building to design. Design exists and there is partial support already, most remaining work is smoothing out some of the rough edges. |
🚙 Parked tasks
List the larger responsibilities that aren't moving forward until I return, such as creating a prototype or planning/conducting research.
-
Item
-Link
📖 References
✅ Issue Tasks
⭕ Opening Tasks
-
Assign to yourself -
Title the issue Coverage for YOUR-NAME from XXXX-XX-XX until XXXX-XX-XX
-
Add any relevant references including direction pages, handbook pages, and so on -
Fill in the Responsibilities table with broad based responsibilities -
Fill in the specific Coverage Tasks with distinct items to complete and assignees -
Manager: Delegate expense approval to your back up team member -
Assign this issue to anyone with a specific task or responsibility assigned to them -
Share this issue in your section, stage, and group Slack channels, and with your manager -
Ensure your PTO Ninja auto-responder points team members to this issue -
Update your GitLab.com status with your out of office dates -
(Optional) Add an issue comment for your retrospective titled: :recycle: Retrospective Thread
❌ Closing Tasks
-
Assign back to yourself and remove others -
Review any Retrospective items with your counterparts and manager