2019-08-26 - Triage report for "group::analytics"
Hi, @valexieva @dennis @lmcandrew
This is a group or stage level triage package 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
-
#7168 (closed) Includes merge request approval in contribution/cycle analytics ~"GitLab Enterprise Edition", Manage [DEPRECATED], approvals, customer, ~"cycle analytics", devopsmanage, feature, ~"group::analytics" -
#4422 Create an API endpoint for global contribution analytics ~"GitLab Enterprise Edition", Manage [DEPRECATED], ~"P3", ~"Platform [DEPRECATED]", ~"S3", analytics, api, backend, customer, devopsmanage, feature, ~"group::analytics" -
#1036 Export contributor analytics ~"GitLab Enterprise Edition", Manage [DEPRECATED], analytics, customer, devopsmanage, feature, ~"group::analytics", reporting
Unscheduled feature (non-customer)
-
#6848 Instance/project-scoped Contribution Analytics ~"GitLab Enterprise Edition", Manage [DEPRECATED], ~"Platform [DEPRECATED]", UX, analytics, backend, devopsmanage, feature, frontend, ~"group::analytics" -
#6101 Contribution analytics - sort contributor's closed issues by the sum of their weight ~"GitLab Enterprise Edition", Manage [DEPRECATED], ~"Platform [DEPRECATED]", UX, analytics, devopsmanage, feature, ~"group::analytics" -
#1087 (closed) Add kanban charts ~"GitLab Enterprise Edition", Manage [DEPRECATED], auto updated, ~"cycle analytics", devopsmanage, feature, ~"group::analytics", potential proposal
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.
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.
| ~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
|---|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 0 | 0 | 0 | 0 |
| ~P3 | 0 | 0 | 0 | 0 | 0 |
| ~P4 | 0 | 0 | 0 | 0 | 0 |
| ~"No priority" | 0 | 0 | 1 | 0 | 2 |
Unscheduled ~bug (non-customer)
-
#13343 (closed) Issues > Analytics display different issues created ~"GitLab Enterprise Edition", ~"S3", ~"bug", devopsmanage, ~"group::analytics", issues -
#8308 (closed) Milestones from Archived Project are Displayed at Group Level ~"GitLab Enterprise Edition", Manage [DEPRECATED], ~"bug", devopsmanage, ~"group::analytics", milestones, project
This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook: