Is there an existing issue for this?
Summary
Problem
The current dashboard functionality is primarily focused on work items. However, projects themselves are an important overarching data type within a workspace, and there is currently no comparable way to visualize or analyze project-level data over time. The "Analytics" section is just not detailed enough.
For teams managing many projects, this makes it difficult to answer questions about the project portfolio as a whole without exporting data or using external reporting tools.
Proposed functionality
Extend the existing dashboard functionality so that Projects can be used as a data source, in addition to work items.
Ideally, dashboard widgets could:
- aggregate and count projects
- group projects by properties such as labels, state, lead, team, etc.
- filter projects by their properties
- use project creation/completion dates as a time dimension
- aggregate numerical project-level fields or metrics
- display the results using the existing dashboard visualization options
Example use cases
1. Projects created by label over time
A bar or line chart showing how many projects with a specific label (e.g. "XY") were created each month during the last 12 months.
For example:
X-axis: Month
Y-axis: Number of projects created
Filter: Project label = "XY"
This would make it possible to understand how the number or type of projects being initiated changes over time.
2. Allocated hours per project over time
A stacked bar chart showing how many hours were allocated to each project over the last year.
For example:
X-axis: Month
Y-axis: Allocated hours
Stack/group by: Project
Time range: Last 12 months
This could help with understanding resource allocation and how capacity is distributed across the project portfolio.
Suggested direction
Rather than introducing a separate project-reporting feature, it would be great if the existing dashboard/query model could simply support selecting the underlying entity being analyzed:
Data source: Work Items / Projects
The same filtering, grouping, aggregation, time-range, and visualization capabilities could then be applied to project properties where applicable.
This would make the dashboard system more flexible while keeping the reporting experience consistent.
Why should this be worked on?
Projects are a higher-level organizational entity than individual work items. For many teams, reporting is therefore needed at both levels:
Work item analytics → How is the work progressing?
Project analytics → What kinds of projects are we running, how many are we running, and how are resources distributed between them?
Supporting projects as a first-class dashboard data source would turn Plane dashboards into a much more useful tool for portfolio-level reporting, capacity planning, and historical analysis.
Is there an existing issue for this?
Summary
Problem
The current dashboard functionality is primarily focused on work items. However, projects themselves are an important overarching data type within a workspace, and there is currently no comparable way to visualize or analyze project-level data over time. The "Analytics" section is just not detailed enough.
For teams managing many projects, this makes it difficult to answer questions about the project portfolio as a whole without exporting data or using external reporting tools.
Proposed functionality
Extend the existing dashboard functionality so that Projects can be used as a data source, in addition to work items.
Ideally, dashboard widgets could:
Example use cases
1. Projects created by label over time
A bar or line chart showing how many projects with a specific label (e.g.
"XY") were created each month during the last 12 months.For example:
This would make it possible to understand how the number or type of projects being initiated changes over time.
2. Allocated hours per project over time
A stacked bar chart showing how many hours were allocated to each project over the last year.
For example:
This could help with understanding resource allocation and how capacity is distributed across the project portfolio.
Suggested direction
Rather than introducing a separate project-reporting feature, it would be great if the existing dashboard/query model could simply support selecting the underlying entity being analyzed:
The same filtering, grouping, aggregation, time-range, and visualization capabilities could then be applied to project properties where applicable.
This would make the dashboard system more flexible while keeping the reporting experience consistent.
Why should this be worked on?
Projects are a higher-level organizational entity than individual work items. For many teams, reporting is therefore needed at both levels:
Work item analytics → How is the work progressing?
Project analytics → What kinds of projects are we running, how many are we running, and how are resources distributed between them?
Supporting projects as a first-class dashboard data source would turn Plane dashboards into a much more useful tool for portfolio-level reporting, capacity planning, and historical analysis.