Feature Requests

In the SEI Productivity dashboard, the Work Completed Per Dev report classifies work items as Features or Bugs based on the Work Type filters in Team Settings. Any work item type that does not match those filters is grouped under Other rather than dropped, so it still contributes to the completed-work totals when viewing All or Other . Some work item types are not meaningful units of delivered work for this metric. Test Cases are the common example: they are created and closed as part of QA activity, but counting them as completed work skews the per-developer throughput numbers and the Other bucket. What we'd like A way to exclude one or more work item types from the Work Completed Per Dev report entirely, so they never count toward completed work in any grouping. Ideally one of: A Not Equals (or exclude) condition on the Work Type configuration, so a team can say Issue Type Not Equals Test Case . A dedicated "exclude these work item types" list in Team Settings that removes selected types from the report before totals are calculated. Either option would solve the need. A team-level setting is preferred so it can be aligned to each team's actual workflow. Why this matters Including non-delivery work item types (like Test Cases) inflates completed-work counts and distorts per-developer throughput trends. Today these types can be kept out of the Feature and Bug views by grouping, but there is no way to remove them from the report entirely, so the All and Other totals remain skewed. Teams that track Test Cases (or other administrative item types) as first-class work items in their board need this to get an accurate productivity picture. Example A team on Azure Boards tracks Product Backlog Item and Feature as features, and Bug as bugs. Test Cases are closed frequently as part of QA. Those Test Cases are not counted as Features or Bugs, but they still appear in the Other group and in the overall completed-work totals, with no way to exclude the Test Case type outright. Today's workaround (and why it is not enough) Grouping the report by Features or Bugs hides Test Cases from that view, but they still count in All / Other totals. There is no native way to remove a work item type from the report entirely.

Request to enable the Release Orchestration module for testing purposes and to understand the features. Best Regards Sai

Send notifications when an integration status changes to: Critical Needs Attention Send alerts after a configurable number of consecutive ingestion failures. Display the last successful ingestion timestamp directly in the Integrations list. Display the first failed ingestion timestamp for the current failure period. Display the number of consecutive failed ingestions. Provide filtering and search capabilities for ingestion logs by: Date range Status Integration Increase accessible ingestion log history to support troubleshooting and audits. Add integration health summary information: Current status Last successful ingestion Last failed ingestion Consecutive failure count Business impact: Integration failures can remain unnoticed for extended periods. The proposed enhancements would allow teams to quickly identify, investigate, and respond to integration issues without manually reviewing ingestion logs.

Hi team, We have a use case that requires the export of the data in the sprint metrics. Currently this option is only available in the UI for the DORA metrics which only allows us to have a partial view of the entire team performance. We would like the option from the UI to also export the Sprint Metrics of a certain team. If there is any further information required from our side feel free to ask. Kind regards.

In order to filter the production deployment pipelines in Harness, we need the filter "Environment Type" in the pipeline filters for the DORA workflow profile.

I am managing the Deluxe RDC Indra team. I am not able to see the trellis score for my team. My team is not configured in trellis it seems. Can you please configure the profile? Team members Sagar Kothadiya (Dev) Rohan Sonar (Dev) Ryan Schwantes (Dev) Nikhil Shende (Dev) Dinup M (Dev) Dhanshree Umarani (Dev) Sapan Giri (Dev) Jereez A (Dev) Bharati Chabukswar (QA) Adarsh Vacchani (QA)

Based on the feedback we’ve received from users, we need to change the name of the “Custom” tab, as the feedback indicated that it doesn’t accurately reflect what’s displayed in that section of the platform.

Hi team, good day, We have a use case for the organization chart that is seen every time you create a new org tree in SEI 2.0, after the org tree is created that view of the organization chart is no longer accessible which means we need to go into the org tree creation tab every time we want to see that view again. We would like to be able to consult that view at any given time without having to go into the org tree creation tab so it can be used as an occasional organization chart review option. Any questions or further information needed feel free to ask, kind regards.

For incident management, we would like to have the assignment groups pre-pulled even if they have no data so we can pre-assign for new teams etc..

In order to improve user's experience from Canvas menu, we should add a few text tooltips in order to guide the users regarding metrics definition.