Release Update 09/15/2025

Unified Insights

PR Cycle Time metric Addition for Pull Request (PR) Statistics KPI

The DevEx Dashboard's PR Stats now includes the PR Cycle Time metric, improving insight into development and release pipeline speed and efficiency. PR Cycle Time tracks the entire duration from pull request creation to deployment, encompassing review, approval, merging, and deployment, to assess delivery speed and team efficiency.

Key Highlights:

  • The metric calculates the average elapsed time between the pull request creation timestamp and deployment timestamp, with units configurable as hours or days.

  • Table columns and expanded chart visualization options have been introduced, including bar charts segmented by week, day, or month.

  • Pull requests that have not been deployed are clearly flagged with the message “No Deployment Found.”

  • A tabular view listing individual PRs alongside their respective cycle times has been provisionally added.

Advanced Commit & PR Filtering Options to Refine Dashboard Data Views

The DevEx dashboard allows users to filter out merge, bot, or unauthored commits and PRs for more accurate data.

Key highlights:

  • Enhanced Data Accuracy: Merge commits, bot commits, and unauthored PRs are excluded, ensuring only relevant contributions are counted and improving metric accuracy.

  • Improved User Control: Separate toggles are provided to customize views, enabling tailored filtering for commits and PRs based on individual preferences.

  • Consistent Data Presentation: Filtering options are uniformly integrated below hierarchy filters and supported in custom dashboards, ensuring consistency across views.

Precise Branch-Level Filtering for Accurate Sonar Coverage Metrics

Branch-level filtering in Sonar Projects improves coverage metric accuracy by allowing users to filter data by specific branches. What's New:

  • Branch-level filtering is now available directly at the Sonar Project level, providing finer control over coverage data.

  • Three new filters have been added under a dedicated tab:

    • Project

    • Sonar Project

    • Branches

  • Multiple Sonar projects can be selected simultaneously, with branch filters applied only to branches common across all selected projects.

  • This filtering capability applies to Sonar ratings, code coverage trends, and detailed tables, improving visibility into code quality across branches.

Enhancements for KPIs in Velocity View of Sprint Velocity Dashboard

Significant improvements have been made to the Velocity View within the Sprint Velocity Dashboard increase flexibility in data presentation and ensure critical metrics are accurately represented and easy to interpret. What's New:

  • Column widths within the performance table have been made adjustable, allowing for optimized display space tailored to longer fields such as Offering, improving readability.

  • Sorting functionality has been enabled for all columns, enabling users to dynamically organize and explore the data.

  • Display logic for velocity metrics has been refined so that when Committed or Completed Story Points are zero, the value ‘0’ is shown instead of ‘NA.’ This change eliminates inaccurate Say/Do % values and improves metric accuracy.

Velocity Metrics Contributor Count Update

Sprint analysis accuracy has been increased by ensuring that only currently assigned contributors are counted in team size metrics. This refinement delivers a more precise representation of team involvement during sprint execution.

What's New:

  • Contributor count has been adjusted to include only the latest or currently assigned user for each ticket based on sprint data.

  • Prior assignees are excluded from the team size calculation.

  • Tickets with multiple assignees are evaluated to ensure that only the most recent assignee is counted, maintaining metric accuracy.

  • Tickets without a currently assigned user are omitted from the count; historical assignees are disregarded.

  • Counts of multiple assignees per ticket have been eliminated, with only the active contributor being reflected in reports.

Additional Capabilities

  • Copilot Codebase Activity UI Label Changes Copilot Codebase Activity's UI labels have been refined for better clarity and consistency. These updates improve the interpretability of metrics and tooltips, providing clearer communication regarding pull request status and associated metrics within the Copilot interface.

  • Pipeline Stats and Pipeline Stage Detail Table Filtering Enhancement To improve the accuracy and relevance of pipeline data analysis, the filtering functionality for pipeline stats and pipeline stage detail tables has been refined. Filters for "Does Not Contain" and "Include" are now restricted exclusively to the step name and step type fields, ensuring targeted and meaningful filtering results.

Platform

Release Update Platform Introducing Ownership Transfer for Tasks

The capability to transfer ownership of Tasks has been introduced to close gaps in the user offboarding process. This allows tasks to be reassigned seamlessly when a user departs, safeguarding workflow continuity and maintaining organizational security.

Key Highlights:

  • Ownership Transfer Access: The ownership transfer option is accessible to users with Administrator roles or those currently owning the Task.

  • User Selection: Users can select a new Task owner from the organization’s active user list.

  • Audit Trail Transparency: All ownership transfers are logged in the Task activity history, recording details such as who transferred ownership, from whom, to whom, and when.

Addition of Step Completion Timestamp for Pipeline Notifications

Pipeline email and Slack notifications have been improved to include completion timestamps for individual pipeline steps. Users can see exactly when each step finished, providing much clearer insight into pipeline progress. Notifications will display the step name, its status and the completion time.

Salesforce

Improved Filter Functionality for Salesforce PR Validation Dashboard

The PR Validation dashboard has been enhanced to offer users improved flexibility and control when reviewing Pull Request validation results. These filter options allow for faster identification and analysis of PRs based on validation outcomes and target branches.

What’s new:

  • Status Filter: A filter for PR Validation Status is now available on the dashboard. Users can narrow results to PRs with a validation status of Success, Failed, Running, or Queued, making it easier to focus on relevant validation runs.

  • Branch Filter: The new Branch filter allows selection of target branches configured in the Pull Request Validation policy. All available branches for the selected repository are listed, enabling targeted review of validations by branch.

Automatic Deployment Failure for Low Code Coverage

Deployments will now be automatically blocked if the configured code coverage thresholds are not met, ensuring robust and reliable Salesforce code quality. This capability helps teams proactively maintain code quality and comply with best practice standards for Salesforce deployments.

Note: The deployment will fail if code coverage falls below the environment's configured threshold, even if other criteria pass.

Automated PR Template Inclusion for Salesforce Tasks

Opsera automatically populates pull requests (PRs) created via Salesforce workflow tasks with the content of the repository's pull_request_template.md file (if one exists). This capability ensures consistent PR formatting for all generated GitHub PRs, leading to clearer code reviews and improved team collaboration.

SDLC

Capability to Retain Review Comments During Gerrit to GitHub Migration

Opsera ensures all line-level review comments are kept intact during migration from Gerrit to GitHub, even when multiple comments have the same timestamp. Comments are grouped by line number and author to avoid losing any feedback due to time overlaps. This capability helps teams keep a complete and accurate history of code reviews and collaboration.

Last updated