This Epic contains requests for integrating analytics into Boards. Other issues/epics currently tied to other epics: - VSM Analytics - https://gitlab.com/groups/gitlab-org/-/epics/3801 (lots to unpack here) ## Use Cases To Provide Analytics For - Kanban (https://gitlab.com/gitlab-org/gitlab/-/issues/242038) - A pull system uses different metrics than timeboxed planning methodologies -- Cumulative Flow, Lead Time, Cycle Time, and Time in Stage - Timebox (Scrum, XP, and so forth) - Velocity, Volatility, burndown, burnup - Metrics should be surfaced in as close proximity to where planning and work management happens so that they can influence behavior change. If they don't lead to behavior change, they are meaningless. ## Problems w/ current Analytics tab - Reports look at an entire project or group, where as a Board is often times scoped to a team. How can I see my team's analytics within the context of my Board? ## Links - Pivotal Tracker does a fantastic job [surfacing analytics that are applicable to both Kanban and Timeboxed](https://www.pivotaltracker.com/help/articles/analytics_charts_and_reports_overview/) methodologies in a single analytics interface within a project. ## Customer Idea (Feature progress and EBV)  ## Customer Idea (improving burnup/burndown charts by incorporating velocity)  ## Customer Idea (Dashboard)