As a user of SEI Insights,

I want the ability to select individual Jira projects from a project dropdown,

So that I can easily and directly view insights specific to the projects (or repos) I care about, without needing to create or manage collections.

Acceptance Criteria:

Jira Project or SM Repo Dropdown Availability:

A dropdown menu should display all Jira projects or SCM repos associated with the connected Jira instance or SCM Repos.

The dropdown should dynamically fetch and display project names with no manual setup required by users.

Project Selection Behavior:

Users should be able to select one or multiple projects or repos from the dropdown.

Selected projects or repos should directly drive the insights displayed on the page.

Impact on Insights:

Metrics and insights should refresh dynamically to reflect the data from the selected projects or repos, similar to how collections drive insights today.

Fallback to Collections:

If a user prefers to use collections, the option to select collections should still remain available.

Error Handling:

If the user doesn’t have access to a specific project, the dropdown should either:

Exclude those projects, or Display an appropriate access error message.

Who are the users?

The primary users for this feature would likely be L1 managers, team leads, or senior leadership who are actively tracking project-level metrics and insights.

L1 Managers/Team Leads: These users often need to quickly drill down into specific projects or repositories to monitor team performance, identify issues, and take corrective actions.

Senior Leadership: While they may not use this feature on a day-to-day basis, senior leaders may still benefit from high-level comparisons across projects to understand broader trends and overall team efficiency.

Why do they want to do this?

The intent goes beyond just a UI visual change; it addresses a functional need:

Ease of Use & Efficiency:

Selecting specific projects directly from a dropdown simplifies the workflow.

It avoids the complexity of creating and managing collections, which can be time-consuming for users who only want to focus on a specific project or two.

Identifying Bottlenecks or Trends:

Users want to drill into individual Jira projects or repositories to identify bottlenecks (e.g., PR cycle time, deployment delays, etc.) or focus on areas needing improvement.

It enables project-specific insights, which helps in decision-making and driving performance improvements.

Flexibility:

While collections work for broader views, users need the flexibility to quickly switch focus to a specific project and immediately see relevant insights without additional configuration.