Release Update 08/04/2025
Unified Insights
New Capabilities for GitHub Copilot Reports
Introducing the Premium Requests Metric in the Copilot Dashboard
A Premium Requests metric has been integrated into the Copilot Dashboard to deliver detailed insights into premium API consumption, quota violations, user engagement, and model adoption trends.
The dedicated tab consolidates multiple key metrics, allowing users to effectively track and manage premium request activities over time. Users benefit from clear visualizations, including data tiles and charts enabling data-driven decision-making.
Key Highlights:
Data tiles provide quick views of users, violations, models used, and the most popular model with trend info.
Charts track request trends over time and compare model usage between current and previous periods.
Existing dashboard filters enable users to easily filter and analyze data.
Note:
Premium Requests data is currently not accessible via API. To enable reporting in the Copilot Dashboard, administrators must first export Premium Requests data as a CSV file and share it with Opsera.
Once the data is received, Opsera will insert and process it, making premium request analytics visible in the dashboard.
Please ensure CSV exports are provided regularly to keep the Premium Requests dashboard up-to-date.
Enhancements to User Usage Report: Export Functionality and Team-Based Filtering
The Usage Report now offers greater flexibility and accuracy in tracking user activity with detailed exports and team based filtering capabilities.
Key Highlights:
Export Capability: New export button enables downloading a comprehensive list of all users (active and inactive), including each user’s last activity timestamp and total activity count across four selectable time periods.
Team Filter Integration: Team-based filtering is supported and aligns with the main dashboard's Teams filter. Users can filter the usage report data by applying specific GitHub teams to view relevant information.
Introducing User Engagement Metrics
A comprehensive User Engagement Metrics are added to the Copilot Usage Reports.
Users can gain a deeper visibility into how teams are adopting and interacting with Copilot through. The metrics provide both high-level trends and granular, actionable data—empowering teams to optimize Copilot’s value as part of their workflow.
Key Highlights:
Track active users by feature and by team, highlighting areas of high adoption and identifying opportunities for further enablement.
Understand user retention and platform stickiness with weekly and monthly sustained engagement rates.
All engagement metrics are presented with intuitive bar charts and trend lines, with exportable CSVs for easy sharing and analysis.
Easily download user activity reports covering both active and inactive users with each user’s last activity date and total activity count, segmented across selectable time periods.
Note: Access to these User Engagement Metrics requires an enterprise token. Please note that the current GitHub app does not support this API, so upgrading or switching to an enterprise token is necessary to utilize these enhanced reporting capabilities.
Improved Commit Metrics Consistency in Copilot Dashboard
We’ve fixed an issue in the CodeBase Activity section where commit counts were inconsistent between organization and team views.
Key Highlights:
The “Total Commits” count correctly shows team commits as part of the organization’s total.
Selecting “Organization” and “Teams” values from dropdown filters, no longer causes commit counts to exceed the organization’s total commits.
Previous discrepancies caused by adding team filters have been resolved.
Enhanced Pipeline Stats KPI with New Duration Metrics for Deeper Execution Insights
The Pipeline Stats KPI has been enhanced with new duration metrics, offering deeper insights into pipeline execution times. Within the expanded KPI view, users can view the Minimum, Maximum, and Median Durations of pipeline runs as separate data tiles.
Key Highlights:
The metrics for Minimum Duration, Maximum Duration, and Median Duration are added as tiles for detailed pipeline timing insights.
These duration metrics appear immediately after the Total Pipelines count for easy access.
To improve clarity, the original five metrics have been moved to a separate row below the new duration tiles.
Introducing New Metrics for DevEx Dashboard
Developer Throughput Summary KPI
Developer Throughput Summary KPI, offers insights into development efficiency through three core metrics: Coding Time, Review Time, and Pickup Time. These metrics enable teams to effectively monitor workload dynamics throughout the pull request lifecycle.
Key Highlights:
Comprehensive Throughput Insights: Teams can track crucial phases of development (Coding, Review, and Pickup times) to identify delays and boost efficiency across the PR process.
Flexible Filtering & Mapping: Analyze data tailored to your needs with filters for organization, team, project, module, repository, and Scrum team mappings.
Actionable Trend Analysis: View average and median values per metric, compare them with previous periods, and utilize trend indicators to monitor improvements or setbacks over time.
Artifacts Statistics KPI
The Artifacts KPI in the DevEx dashboard delivers focused visibility into artifact-related metrics.
By centralizing key details such as creation data, download frequency, and ownership, teams can quickly see which builds matter most, who’s using them, and how artifact usage is evolving.It streamlines artifact management by centralizing activity, enabling data-driven decisions on usage and retention, and ensuring compliance with a full audit trail.
Key Highlights:
Targeted Artifact Tracking: Provides clear insights into artifact metrics filtered by repository and project.
Efficient Access: Every artifact includes direct links for easy retrieval, making validation or sharing a one-click process.
Custom Filtering for Teams: Filter data by repository names ensuring each team sees only their most relevant assets.
Artifacts Statistics KPI has been moved from NX to NX01. Please refer to the NX01 dashboard for the latest artifact metrics and management features.
Enhanced DevEx Group Mappings with GitHub Teams for Improved Team-Based Reporting
The ability to map GitHub Teams along with Project URLs are supported for DevEX KPIs during the tool mapping process. Users can now easily select from all available GitHub Teams when creating group mappings, and the dashboard reflects data accurately for only those teams with relevant activity.
Key Highlights:
Complete GitHub Teams Listing: The filter section in DevEx group mappings now displays the full list of GitHub Teams, ensuring users have access to all team options for mapping and filtering.
Seamless Team Selection: Users can select and map any GitHub Team alongside Project URLs, enhancing flexibility in group configuration.
Dynamic Filtering by Teams: The dashboard filter supports team mappings, enabling users to easily filter reports and metrics by their selected GitHub Teams.
Accurate Team Data Display: Mapped teams with actual data are correctly represented in dashboard views, enabling focused analysis and reporting on active teams.
Additional Capabilities
The Defect Density SonarQube logic has been updated to improve data visibility on the dashboard.
Instead of showing the most recently scanned projects with a maximum limit of 30, the dashboard displays the top 30 projects with the highest number of issues, sorted in descending order. This ensures that users always see relevant defect density data, focusing on the projects with the most significant number of defects.
The Release Management dashboard supports direct integration with GitHub Actions (GHA) pipelines, joining existing Opsera pipeline support.
Key Highlights:
GitHub Actions/GitHub pipeline workflows are selectable in dashboard filters.
Users can map GHA workflow stages and jobs into standardized environment categories, when performing group mappings.
RM Insights can now track code commits and progress through mapped GHA stages for each Jira ticket, just as with Opsera, delivering clear visibility across all your CI/CD pipelines.
Salesforce
Introducing Delta Code Scan: Targeted Vulnerability Detection for New Salesforce Code
Delta Code Scan is available to be configured in Opsera’s Salesforce Code Analyzer setup.
With this capability, only newly added or changed lines are scanned during Salesforce workflows. This way, legacy issues are excluded, giving you faster scans and focusing reviews on what’s just been written. Learn more on how to enable the delta scan here.
Key Highlights:
Scans Only New/Changed Code: Analysis is limited to newly added or modified lines.
Select Issue Severity: Choose which severities (Critical/High/Medium) to enforce for new code directly on the setup screen.
Pick Rule Categories: Easily include or exclude categories such as Security, JavaScript, Apex, and CodeStyle for targeted coverage.
Clear Rule Counts: See at a glance how many rules are applied per category and severity, helping you understand scan focus.
Quick Actions: Use “Select All,” “Deselect All,” and “Export” for fast configuration changes or to share rule sets.
Automatic Integration: Once the scan rules are integrated, the Delta Scan runs by default in Salesforce workflows.
Note:
Applies to all Salesforce pipelines, tasks, and PR validations using the Code Analyzer tool in Opsera workflows—except the Salesforce Branch Code Scan task.
Delta Scan quality gates must be configured in Validation Rules for the delta scan to activate.
Scanning runs only on files marked as Modified or In Conflict.
Does not support renamed files.
Accurate Task Status Updates for Pull Requests on Protected Branches
The Salesforce to Git Merge Sync and Git to Git Merge Sync tasks have been updated to correctly reflect task status when creating Pull Requests on protected branches.
Previously, tasks were marked as “Failed” if a PR was created but could not be auto-merged due to branch protection rules. Task status now shows "Success" on PR creation, regardless of auto-merge capability, improving reporting and reducing confusion, while still flagging the required manual merges.
Platform
Capabilities for DataOps Pipeline Wizard
Pipeline Actions Supported for DataOps Pipelines
Pipeline actions have been introduced to streamline governance and enhance collaboration across teams. With these capabilities, teams can efficiently perform the following Pipeline actions:
Pipeline following
Template publishing
Duplication
Ownership transfer
Deletion
Audit logging
Configuration review
Accessing contextual help.
RBAC Enhancements for Guest User Permissions
Guest user permissions in DataOps and pipeline management have been modified for better security and governance, aligning with RBAC policies to prevent unauthorized actions.
What’s New:
Start Button Disabled for Guest Users: Guests cannot start pipelines from the normal pipeline interface, preventing unauthorized executions outside approved flows.
Pipeline Execution via DataOps Flow Only: Guest users may run pipelines only through the designated DataOps workflow, ensuring controlled and auditable execution.
Connection Editing Restricted: Guests are blocked from modifying connection details in the DataOps Pipeline Wizard’s Connection tab to protect critical configuration settings.
Pipeline Summary Enhancement: GitHub User Trigger Display
The pipeline summary now displays the GitHub username of the user who triggered the pipeline via a Git push event, instead of showing the pipeline owner’s name. This provides better transparency about who initiated the pipeline, for enhanced traceability.
Key Highlights
When available, the GitHub username is shown, extracted directly from the webhook payload.
If the username is not provided, the summary defaults to showing “Triggered by Webhook.”
Manual and other trigger types continue to display as before, without changes.
User information is carefully parsed from the GitHub webhook to ensure accuracy.
SDLC
SCM to SCM Migration – CSV Upload for Repository Mapping Now Supported via Public API
Opsera’s SCM to SCM Migration feature has been enhanced to support CSV uploads for repository mapping through the Public API. Previously restricted to the UI, this capability now enables automated, programmatic CSV submissions, enhancing integration flexibility and enabling seamless automation within CI/CD pipelines.
Key Highlights:
CSV repository mapping uploads can now be done via the Public API, allowing bulk and automated mappings.
Reduces manual effort in large or repeat migration scenarios by enabling bulk mappings through API calls.
ACR Image Scanning Integration with Lineaje
Images stored in Azure Container Registry (ACR) can now be automatically scanned for SBOM and vulnerabilities using the Lineaje API through Opsera pipelines, giving your DevSecOps teams seamless, real-time risk analysis and improved supply chain visibility.
Key Highlights:
End-to-end automation fetches image details from ACR, triggers Lineaje scans, and retrieves SBOM and vulnerability data.
Results are posted to both the Opsera pipeline console and the Lineaje UI, giving unified and actionable insights.
Security and compliance workflows are streamlined to ensure only secure images move forward.
Last updated