Feature Requests

Right now we helm delegates setup and the build pods that run are only accepting helm resource values for limits and not allowing to define requests for resources. Looks like it is setting up default value for requests. Is there a way to define requests if not can this feature be added.

Hi Team, It's painful to reach out to SEI Team for checking CI & CD Correlation each time from their DB end. We don't have the visibility for historical data for CI & CD we are completely blind where it's getting deployed or what is the execution number into Harness CD. For better visibility, please introduce a consolidated view of CI & CD stages data from where user can understand: CI is for this particular pipeline & this is the qualifier/Artifact name For the same CD Data: Pipeline Name, Execution Number etc metadata which helps us & empowers end user with better visibility for CI & CD pipelines in question. Widget: Dora Lead time for change Enhancement needed: CI & CD stage data drilldown view (Pipeline & related unique identifier used for CI & CD Correlation)

In workflow for custom CI/CD the stage filter should also include project as a filter. For example for Harness, we want to filter pipelines based on project they are in.

We prefer that non-admin users do not see the integration failure notifications. Since SEI viewers can’t take action on these notifications anyway, it makes sense to hide them from their view.

We request an enhancement to user role permissions at the project level, specifically for users who have access to collection settings, allowing them to create, edit, delete, and save their own DORA profiles within the rights granted in the collection settings. Currently, these actions fall under configuration settings, which restricts workflow efficiency and introduces an RBAC risk, as only configuration admins can make updates. This limitation hinders the ability to update new product profiles while maintaining compliance. We propose shifting DORA profile management permissions from Configuration Settings to Collections RBAC Rights, enabling better role-based access control, improving agility in updating product profiles.

Today the correlation engine relies on commit titles, pull request (PR) titles, and branch names to associate data between the issue management system and the source code manager. However due to the lack of standardization this often results in incorrect mappings between issues and PRs. Consequently the lead time calculations may not accurately reflect the true picture of development timelines. Proposed Enhancement - Introduce a standardized correlation mechanism to improve the accuracy of issue-to-PR mapping.

We are looking to get insights into new hire onboarding, The requirements we have are This should be a separate collection Users get added/removed in a automated way For each user insights should be shown from the day they joined, till their 90th day The insights should show data for commits, PRs merged, tickets resolved, lines of code, PRs reviewed

Currently, for the SCM PRs Report widget, the expanded report does not include PR reviewer details in the result PR list. Could we please add this information as well? This would provide more comprehensive insights into the report.

Read via API: list all the PRs with creator, reviewer, and stage time duration information.

As a user of SEI and the Dev Insights dashboard, I would like header in the PR REVIEW REPORT to be interactive and able to filter the table based on selecting one of the items. It is confusing as a user to see the header, which is only view-only, and not be able to filter the data based on the top level item. Currently, a use has to go to the bottom of the table and unselect items from the legend, which is not intuitive UI/UX design