Is there an existing issue for this?
Summary
Related to #9642: Project-level analytics in dashboards
Summary
Dashboards and PQL currently do not appear to support filtering by Team Space.
This makes it difficult to create dashboards that are scoped to a specific Team Space, even though Team Spaces are intended to provide a dedicated context for a group of related projects and their work.
Problem
As a Team Space admin or member, I want to create and view dashboards that are scoped to the Team Space I am currently in, so that the dashboard represents the work belonging to that Team Space rather than the entire workspace.
Currently, when creating a dashboard using PQL, there is no Team Space filter available.
My assumption is that this is because a Team Space is associated with a Project, rather than directly with individual Work Items. Since dashboards currently query Work Items rather than Projects, project-level properties such as the Team Space cannot be used for filtering.
This seems closely related to #9642, which proposes making Projects available as a first-class dashboard data source.
Proposed functionality
Ideally, dashboards should support Team Space context in one or both of the following ways:
-
Team Space as a PQL filter
Allow queries to filter work items based on the Team Space of their parent Project.
Conceptually:
Team Space = "Engineering"
This would allow a dashboard to aggregate work items across all Projects belonging to a specific Team Space.
-
Automatically scope dashboards created inside a Team Space
When a dashboard is created or viewed from within a Team Space, it should be possible to scope that dashboard to the current Team Space.
This would make the dashboard behave consistently with the surrounding Team Space context.
Example use cases
A Team Space such as Engineering contains several Projects:
- Backend
- Web App
- Mobile App
- Infrastructure
As a member of the Engineering Team Space, I would like to create dashboards showing:
- Work items by state across all Engineering projects
- Work items completed over time
- Work items by assignee
- Overdue work items
- Work items by priority
- Cycle or module progress across projects in the Team Space
Today, there is no straightforward way to express:
Show me work items whose Project belongs to this Team Space.
Expected behavior
When working inside a Team Space, I should be able to create a dashboard whose data is limited to that Team Space.
For example:
Team Space → Engineering → Dashboard
The dashboard should either automatically inherit the Engineering Team Space as its scope, or allow me to explicitly select:
Filter: Team Space = Engineering
Why should this be worked on?
Team Spaces provide an organizational layer above Projects. Without the ability to use that layer in dashboards, Team Space members cannot easily get an aggregated view of the work happening across their projects.
Supporting Team Space filtering would make dashboards much more useful for team-level reporting:
- Project dashboard: How is this individual project progressing?
- Team Space dashboard: How is our team progressing across all of its projects?
- Workspace dashboard: How is the organization progressing overall?
This would also complement #9642. If dashboards gain awareness of Projects and their properties, Team Space membership could naturally become a filterable dimension of dashboard queries.
Is there an existing issue for this?
Summary
Related to #9642: Project-level analytics in dashboards
Summary
Dashboards and PQL currently do not appear to support filtering by Team Space.
This makes it difficult to create dashboards that are scoped to a specific Team Space, even though Team Spaces are intended to provide a dedicated context for a group of related projects and their work.
Problem
As a Team Space admin or member, I want to create and view dashboards that are scoped to the Team Space I am currently in, so that the dashboard represents the work belonging to that Team Space rather than the entire workspace.
Currently, when creating a dashboard using PQL, there is no
Team Spacefilter available.My assumption is that this is because a Team Space is associated with a Project, rather than directly with individual Work Items. Since dashboards currently query Work Items rather than Projects, project-level properties such as the Team Space cannot be used for filtering.
This seems closely related to #9642, which proposes making Projects available as a first-class dashboard data source.
Proposed functionality
Ideally, dashboards should support Team Space context in one or both of the following ways:
Team Space as a PQL filter
Allow queries to filter work items based on the Team Space of their parent Project.
Conceptually:
Team Space = "Engineering"This would allow a dashboard to aggregate work items across all Projects belonging to a specific Team Space.
Automatically scope dashboards created inside a Team Space
When a dashboard is created or viewed from within a Team Space, it should be possible to scope that dashboard to the current Team Space.
This would make the dashboard behave consistently with the surrounding Team Space context.
Example use cases
A Team Space such as Engineering contains several Projects:
As a member of the Engineering Team Space, I would like to create dashboards showing:
Today, there is no straightforward way to express:
Expected behavior
When working inside a Team Space, I should be able to create a dashboard whose data is limited to that Team Space.
For example:
Team Space → Engineering → Dashboard
The dashboard should either automatically inherit the Engineering Team Space as its scope, or allow me to explicitly select:
Filter: Team Space = Engineering
Why should this be worked on?
Team Spaces provide an organizational layer above Projects. Without the ability to use that layer in dashboards, Team Space members cannot easily get an aggregated view of the work happening across their projects.
Supporting Team Space filtering would make dashboards much more useful for team-level reporting:
This would also complement #9642. If dashboards gain awareness of Projects and their properties, Team Space membership could naturally become a filterable dimension of dashboard queries.