[FEAT] Add the selection of a specific project in the analytics/work-item page

[LADsy8]

Scope

UI + API

Primary area

Workspaces / Projects / Issues

Problem

Type / Priority

Feature / Medium

Summary

When a user selects a specific project from the project dropdown menu in the analytics pages, the dashboard does not filter or update to display data exclusively for that project.

Current Behavior (Evidence)

Selecting a specific project from the top-right dropdown menu results in the following:

• The URL route remains unchanged.
• The two affected analytics pages do not re-render or update their data.
• The "Active Projects" list remains identical to the "All Projects" view.
• The listed priorities do not change based on the selection.
• No relevant errors or logs appear in the npm console.

Proposed solution

• Update the analytics work items and overview pages so that data dynamically filters based on the selected project (when an option other than "All Projects" is chosen).
• Implement or update the backend/API routes to fetch analytics data specific to a single project rather than defaulting to the global "All Projects" dataset.

Alternatives considered

No response

Acceptance criteria

• AC1: Project Selection and Routing

  Given a user is on an analytics page (Work Items or Overview), when they select a specific project from the top-right dropdown menu, then the application updates the URL route (or query parameters) to reflect the chosen project ID.

• AC2: Data Filtering for Single Projects

  Given a user has selected a specific project, when the analytics pages load or update, then all displayed metrics, active projects lists, and priorities are filtered to show data exclusively for that selected project.

• AC3: Fallback to "All Projects"

  Given a user selects the "All Projects" option from the dropdown menu, then the analytics pages reset to display aggregated global data and update the URL/state accordingly.

• AC4: API Support for Single Project Analytics

  Given the frontend requests analytics data for a specific project, when the API is called, then the backend successfully handles the request and returns scoped data for that project rather than returning the global dataset.

Additional context

this:

and this:

are the same even thought i have selected a specific project in the first image