Feature Requests

Currently the definitions for a collection are all "AND", but having the option to use logical operators of "AND" or "OR" would allow for more appropriate definitions.

In Trellis, currently the Rework Metric includes the activity of adding lines to an existing file as part of it's calculation and lowers the productivity score as a result. Often times, this activity of adding lines to an existing file is related to creating a new function / feature and would be a positive behavior as opposed to just rewriting existing lines. Requesting to have the option to select that adding lines to an existing file be a positive or to remove this from being categorized as rework and instead viewed as a new metric like "enhancement".

Dear Product Team, We would love to have the possibility to (in a simple way - tabular), compare different DORA metrics between collections (assets, teams, etc). This way, without drill-through, one can quickly see the team's performances, etc. Like Trellis, just with DORA - quite handy for C level and upper management. Thanks in advance

For the AI reports shown in AI insights page https://app.harness.io/ng/account/VUigKq0wTpuKAN-bibECGg/module/sei/orgs/default/projects/DW/ai-productivity-insights/report/42e07a5f-a31f-44a1-80c5-f7c63fe1631c?reportType=ai-insights-plus It will be helpful to provide the drill down view for Average Number of PR's Average number of Merges PR lead time Average commits Average lines May be link to trellis score as well for the individuals

The metrics which are calculated in Trellis are not giving us the latest information. Regardless of which time period is selected on top, the metrics are displayed for Last Month, Quarter, Two Quarters or 12 Months. So, if the team is not doing well at the moment, they will know that in January. Or if they improved something in their practices in January, they would need to wait until February to see these numbers updated. Request: A possibility to make this more current, or add more options in this spreadsheet. Ideally, we want to be able to track this including the current development, rather than retrospectively.

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.

As an Engineering Organization, we would like to integrate the Wiki platform with Harness to monitor metrics for some of our teams. This integration will enable us to track activities related to document creation and updates effectively. We use Atlassian Confluence as our internal Wiki platform. Your insights or suggestions on implementing this would be greatly appreciated.

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.