Release Update 11/17/2025

Unified Insights

Introducing Role Based Access Control (RBAC) for Group Mappings

This release brings powerful Role-Based Access Control (RBAC) to Group Mappings, delivering enhanced security and a personalized experience across your dashboards and data filters.

Key Highlights:

• Stronger Security: Role-based restrictions ensure only authorized users can access project-level data.

• Personalized User Experience: Each user’s dashboard and filter options are tailored based on their assigned roles, which improves usability and ensures users only see information that matters to them.​

• Scalable Access Management: Easily adjust access levels as teams grow, without manual, error-prone updates.

Executive Summary Dashboard Enhancements

Deeper insights and flexible reporting capabilities have been delivered in the latest update to the Executive Summary KPI.

Key Highlights:

• At-a-Glance Trends: Visual indicators such as arrows and percentage changes highlight what’s improving or needs attention.

• Summary Filter Enhancement:

  • Developer Hourly Rate Configuration: Customers can set the developer hourly rate in the filters tab of Copilot Reports. The default is $75.

  • Increased Report Accuracy: The Executive Summary automatically incorporates the configured hourly rate, ensuring that cost and savings calculations in the summary are precise and relevant to individual organization rates.

Introducing New Metrics for Pull Request Statistics Dashboard

Teams can get more actionable visibility into their pull-request workflows with the updated PR Stats Dashboard

The Pull Request (PR) Statistics Dashboard has been enhanced to provide teams with deeper insights into their code review and merge workflows.

Key Highlights:

• PR Rejection Rate: This metric shows the percentage of pull requests that were closed without being merged. It helps teams understand how often PRs are rejected, highlighting potential issues in code quality.

• PR Approval Rate: This KPI represents the percentage of pull requests successfully approved and merged. Monitoring this metric offers insight into team collaboration effectiveness.

Velocity Trend Line Added to Scrum Teams KPI

The Velocity by Scrum Teams KPI features a velocity trend line, giving Scrum teams a powerful way to visualize and analyze velocity changes across selected periods.

Key Highlights:

• Velocity Trend Line Overview: A velocity trend line allows teams to quickly gauge whether delivery output is rising, stable, or declining.

• Actual vs Committed Story Points: Teams can compare actual delivered story points against commitments to assess delivery consistency across sprints.

Additional Capabilities

Enhancements to AI Code Comparison Dashboards

The dashboard delivers improved visual consistency, user interaction, and guidance to make data easier to understand and actionable.Chart widths, colors, legends, and axis formats have been standardized for a cleaner, more professional look, while pop-up interactions have been refined for smoother expansion, and filter text resized for better visual balance.

PR Approval Rate Calculation Update

The “PR Approval Rate” calculation has been refined to ensure more accurate reflection of review activity. The updated formula only includes pull requests that were actually reviewed, aligning the metric with real engineering workflows.

New Formula

PR Approval Rate = PR Approved ÷ PR Reviewed Here, PR Review counts only those pull requests with non-zero review time (as tracked in the PR Size KPI).

Track ServiceNow Incidents in MTTR KPI

Users can connect ServiceNow integration to capture incident data directly in the DORA Dashboard’s MTTR (Mean Time to Resolve) KPI. This capability provides a more complete view of your resolution performance by including incidents tracked in ServiceNow.

Salesforce

Selective Pull Request (PR) Validation for Salesforce DevOps

Greater control is now provided over when pull request validations are executed in Opsera

A selective configuration has been introduced, allowing validation checks to be limited to pull requests created through Opsera or extended to all pull requests (PR’s created outside of Opsera), as determined by policy selection. This selection enables organisations to execute PR validations specific to the ones created through Opsera.

Key Highlights

• Default Behavior: By default, validation runs for all pull requests, regardless of their origin.

• Policy Toggle for Validation Scope:The “Disable validation for Pull Requests created outside of Opsera” toggle controls whether validations apply only to Opsera-initiated pull requests or to all. If enabled, external pull requests are skipped (automatically marked as “Success”), and the console displays a relevant status message.