Monitor:Respond 16.1 Planning issue
Planning Boards
Goals for the milestone:
- Complete clean up of deprecation and removals
- Enable Service Desk Sisense dashboard to be built
- Ship 3 Release Post worthy Service Desk issues
- Spike on building a service desk work item
Note on capacity: our capacity for %16.1 will be lower than a typical milestone. Several public holidays fall during May.
Team members may also opt-in (and are encouraged!) to participate in the Ops Hackathon week from 2023-05-22 until 2023-05-30. FY24-Q2 - Ops Hackathon Week (gitlab-org&8712 - closed)
OKRs for FY24-Q2:
- https://gitlab.com/gitlab-com/gitlab-OKRs/-/work_items/2912+
- https://gitlab.com/gitlab-com/gitlab-OKRs/-/work_items/2913+
Scope of Work
For goal 3, release Post worthy items (in priority order)
- Service desk settings when issue tracker is off (gitlab-org/gitlab#3292 - closed) • Rajendra Kadam • 16.1
- Service Desk: retain name from the e-mail header (gitlab-org/gitlab#280511) • Unassigned • Backlog
- Service Desk: Add external email participants t... (gitlab-org&10636 - closed)
Please note that Add or remove email participants to Service Desk
is an epic with a few distinct deliverables. More details in the epic.
All other issues are prioritized in the Monitor:Respond Planning Board
Seeking Community Contributions
Issues that are great candidates for community contributions are marked with the label Seeking community contributions.
We welcome all contributions and would be happy to support you along the way!
Full list of issues is here
-
Set the Milestone (current Milestone) -
Update the Milestone link for the Monitor:Respond Planning Board -
Set the Due Date for the end of the current Milestone