Skip to content
Snippets Groups Projects

2020-11-02 - Triage report for "group::access"

    • Closed Issue created by 🤖 GitLab Bot 🤖 @gitlab-bot

    Hi, @mushakov @lmcandrew @dennis @dmoraBerlin @mikelong

    This is a group or stage level triage report that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:

    Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:

    • Determine if the issue should be closed if it is no longer relevant or a duplicate.
    • If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
    • Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
    • Once a milestone has been assigned please check off the box for that issue.
    • Please work with your team to complete the list by the due date set.

    Feature Proposal Section

    For the following feature proposals. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.

    Unscheduled ~feature with customer

    Unscheduled ~feature (non-customer)

    Unscheduled UX Debt Issues

    Bug Section

    For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.

    • Engineering Managers: Please add a severity label for those issues without one
    • Product Designers: Please add a severity label to UX ~bug issues without one

    Heatmap for all bugs

    Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.

    severity1 severity2 severity3 severity4 No severity
    priority1 1 1 1 0 1
    priority2 1 37 4 0 0
    priority3 0 9 70 12 7
    priority4 0 2 59 36 1
    No priority 0 0 82 66 204

    Unscheduled frontend ~bug with customer

    Unscheduled frontend ~bug (non-customer)

    Unscheduled ~bug with customer

    Unscheduled ~bug (non-customer)

    Heatmap for ~missed-SLO bugs

    severity1 severity2 severity3 severity4 No severity
    priority1 1 1 0 0 0
    priority2 1 29 0 0 0
    priority3 0 8 0 0 0
    priority4 0 0 0 0 0
    No priority 0 0 0 1 0

    Heatmap for vintage bugs

    severity1 severity2 severity3 severity4 No severity
    priority1 0 0 0 0 0
    priority2 1 5 1 0 0
    priority3 0 5 35 7 1
    priority4 0 1 46 17 0
    No priority 0 0 6 11 41

    This is a group level triage report that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:

    If assignees or people mentioned in this individual triage report need to be amended, please edit group-definition.yml.

    0 of 166 checklist items completed
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    Please register or sign in to reply