Incorporating more Transparency around Customer Quality Bug Due Dates
Purpose
The goal of this issue is to reduce the number of past due quality issues by making their due dates more transparent and discoverable. Currently the GitLab Bot is automatically assigning the Approaching SLO label 14 days before issue's due date. Many of the Development teams are planning the work for their releases between the 1st and 15th of a month. Adding the approaching SLO label around the middle or end of the month would most likely miss our planning process, disrupt the Backlog, or be pushed to the next release.
Recommendations
- Can we apply the approaching SLO label one month before it is due so that we can incorporate it into our Sprint Planning?
- Can we add due dates to customer quality issues to make it even more transparent when an issue needs to be scheduled?
Actions
Edited by Jennifer Li