Release Update 03/09/2026

Unified Insights

Enhanced Leadership Insights with Advanced GitLab Integration and Flexible Team Comparison

The Leadership Dashboard has been significantly upgraded for standardized executive visibility. The enhancement enables tracking of AI adoption, comparison of team performance, and viewing of automated GitLab metrics through flexible, filter-based reporting, eliminating the need for fixed hierarchies.

Key Highlights

• Unified AI Code Assistant Tracking: Replaces "Copilot" with a universal AI Code Assistants category, featuring automated organization mapping for GitLab Duo and repositories to track cross-platform AI impact.

• Three-Level Organizational Hierarchy: Supports dynamic grouping where users can drill down from Organization to Application (viewing aggregated team comparisons) or Application to Project (viewing granular project-level comparisons).

• Simplified Team Comparison Table: Tabular view of all top-quadrant metrics, with each row representing an Application or Project for side-by-side performance analysis.

• Automated GitLab Mappings: Automatically maps GitLab metadata, eliminating manual data work and complex setup for calculating throughput and quality metrics. Read more here

New KPIs Added to SnapLogic Dashboard

New Node-Level Configuration and User Engagement KPIs are added to the SnapLogic Dashboard. These provide deep visibility into platform health and hardware efficiency, enabling users to optimize JVM performance, manage hardware capacity, and track platform adoption via real-time system limits and user activity trends.

Key Highlights

• Comprehensive Infrastructure Monitoring: Provides deep visibility into node-level hardware configuration, including CPU core count, JVM memory allocation percentage, and total swap size, enabling precise capacity planning and system tuning.

• Advanced User Adoption Analytics: Tracks platform growth through Daily, Weekly, and Monthly Active User metrics, helping leadership measure real-time engagement and identify adoption trends.

• Actionable User Insights: Identifies Inactive Users and calculates a weighted User Engagement Score, allowing teams to proactively manage churn risks and monitor overall platform health. Read more here

API Optimization for AI Code Comparison Dashboards

AI Code Comparison dashboards use the latest Cursor and GitHub Copilot API data fields for more accurate backend processing. This upgrade re-maps key KPIs like license utilization and code contribution to granular data points, improving trust in adoption and impact metrics.

Key Highlights

• Enhanced User Utilization Logic: Updates the backend calculations for Leader Board, Score Board, and Cost Analysis KPIs using new allocated vs. active user data fields, ensuring your cost-per-seat metrics reflect actual tool usage.

• Precision Code Acceptance Backend: Remaps the LOC suggested vs. accepted metrics across the Adoption & Developer Experience and Multi-Dimensional Impact dashboards to provide a more accurate calculation of AI code integration.

• Granular Language Metadata Support: Refines the data ingestion for Language Support and Tool Adoption KPIs, allowing the backend to process and compare AI performance across different programming languages with higher fidelity.

Enhanced Leadership View for Sprint Defect Tracking and Productivity Analysis

The Leadership View dashboard includes new Defect Calculation logic and Productivity metrics for more accurate sprint performance tracking. This aids in assessing sprint health and team output by displaying planned vs. closed defects and average story point delivery over completed sprints.

Key Highlights

• Defects Planned Tracking: Defects Planned show the total count of defects linked to a sprint, including those committed at the start and those added while the sprint was in progress.

• Resolved Defect Visibility: Displays Defects Closed as the total number of resolved issues out of the combined planned and newly added defect pool.

• Automated Productivity Calculation: Displays a new Productivity value within the chart view, calculated by Total Story Points Delivered by the Average Number of Contributors/Number of Sprints completed. Read more here

Advanced Filtering for GitHub Issues in DORA Dashboard

DORA metrics fully support GitHub Issues as a primary data source, providing comprehensive delivery insights for the GitHub ecosystem. This enables native measurement of Cycle Time, MTTR, and CFR directly from GitHub projects to gauge velocity and quality.

Key Highlights

• Native GitHub Issues Integration: Users can select GitHub Issues as the source tool within the DORA dashboard, enabling seamless tracking of delivery performance without requiring external task management tools.

• Granular Project and Label Filtering: Supports mandatory Project Name filtering alongside optional Issue Type and Label selections, allowing teams to isolate specific workstreams for more accurate metric calculation.

• Automated MTTR and CFR Tracking: Automatically identifies defects defaulting to the Bug issue type to calculate recovery times and failure rates based on the ratio of defects to total changes.

• End-to-End Cycle Time Measurement: Measures the complete duration from issue creation to resolution for all items matching your defined GitHub filters, providing a clear view of your team's total lead time.

Dedicated Release Manager Role for Controlled Pipeline Execution

The Release Manager role is available in User Management and Role Configuration. This enhances security and compliance by allowing users to manage and trigger deployments with controls for execution and approvals, without modifying pipeline logic.

Key Highlights

• Automatic Role Migration: All users previously assigned to the "Manager" role have been automatically migrated to the Release Manager role, maintaining their existing workflow while clearly defining their operational boundaries.

• Controlled Pipeline Triggering: Users assigned to the Release Manager role can start and run pipelines for approved releases, ensuring deployments happen on schedule without requiring full administrative access.

• Dynamic Runtime Updates: Enables the entry of CR numbers, release IDs, and environment-specific inputs at the time of triggering, ensuring operational data is captured during the release process.

• Release Coordination Controls: Provides the ability to enable or disable specific pipeline stages and approve designated steps, giving release leads manual control over the flow of code.

• Restricted Configuration Access: Protects DevOps process by preventing the modification, creation, or deletion of pipelines and blocking access to global platform settings or user permission management.

JQL Filters Added into Cycle Time for Changes for Precise Issue Tracking

JQL Filter is added to the Cycle Time for Changes, providing granular control over delivery data. This allows users to filter results using saved Jira queries, eliminating noise and backlog items, and ensuring cycle time measurements accurately reflect active development.

Key Highlights

• Targeted Cycle Time Analysis: Allows teams to accurately calculate the speed of high-priority items by isolating specific subsets of work, like tickets with certain labels or components.

• Data Accuracy & Noise Reduction: Filters out hundreds of irrelevant issues or inactive backlog items that typically skew average cycle time, providing a more realistic view of team velocity.

• Dynamic Updates: Automatically updates all Jira-based KPIs on the dashboard to match the parameters defined in the selected JQL query. Read more here

Platform

Accelerate Pipeline Troubleshooting with Historical Run Analysis

Hummingbird AI restores historical pipeline run analysis through the prompt interface, allowing users to query and analyze any of the last 10 pipeline runs. This enables teams to review historical execution data, investigate failures, and compare recent pipeline behavior without leaving the chat interface. Key Highlights

• Prompt-Based Run Queries: Users can request analysis using natural language prompts referencing run count, run number, or relative position (for example, run 24 or last 5 runs).

• Detailed Run Insights: The response includes run status, duration, step-level execution details, and error information for the requested run.

• Out-of-Range Handling: If a requested run falls outside the available 10-run window, the assistant returns a clear message indicating the supported range.

ServiceNow Change Window Validation for CI/CD Pipelines

Opsera pipelines support ServiceNow change window validation. By automatically validating pipeline execution against authorized change windows, this capability reduces the risk of unauthorized changes and improves compliance with change management policies.

Key Highlights

• Automatic Change Window Validation: Pipelines retrieve change request details from ServiceNow and verify whether the current execution time falls within the approved change window. If the execution occurs within the authorized window, the pipeline proceeds automatically and logs a confirmation message.

• Approval Required Outside the Change Window: If a pipeline runs outside the approved change window, execution pauses and transitions to an Approval Pending state. The pipeline resumes only after manual approval is granted, ensuring controlled deployments.

• Secure and Reliable Execution: If communication with the ServiceNow API fails, the pipeline halts safely and records detailed error information to support troubleshooting and auditing.

User Management Capabilities

• Enhanced Editing of Existing User Details

User Management supports editing of selected user profile details to help administrators maintain accurate user information. Admins can update non-identity fields while core identity attributes remain read-only when sourced from the login provider.

Key Highlights

• Read-Only Identity Fields: First Name, Last Name, and Email remain non-editable and display an informational note indicating they are sourced from the login provider for federated users.

• User Status Indicator: The Active field has been replaced with a User is Deactivated indicator when an account is inactive.

• Improved User Registration and Role Management

User Management requires explicit role selection during user registration, preventing automatic assignment of the Guest role. The Users list displays each user’s assigned site role, and the Site Roles dashboard includes visibility of Guest users for auditing. Additionally, the Manager role has permission to enable or disable pipeline stages, allowing delegated pipeline management without requiring administrator access. This improves role governance and provides clearer visibility of user access across the system.

• Enhanced Group Ownership Management

Group Management allows administrators to update the Owner field for existing groups. This enables organizations to maintain accurate ownership when responsibilities change and ensures proper administration and notifications.

Key Highlights:

• Editable Group Owner Field: Group administrators and organization admins can update the Owner email address directly from the Group Management interface.

• Ownership Validation: The system validates that the entered email address follows the correct format and corresponds to an existing Opsera user.

• Audit and Notifications: Ownership changes are recorded in the audit trail, and notification emails are sent to both the previous and new owners.

Role-Based Access and Shared Catalog for IDP Jenkins Jobs

Flexible RBAC permissions are provided to IDP creators for sharing Jenkins jobs with teams via roles or groups, consistent with Pipeline patterns.

Key Highlights:

• Role-Based Permissions: View, execute, and edit access is granted by role or group; Jenkins jobs are cataloged for reuse across teams.

• Controlled Job Access: Permissions are applied to viewing, execution, and management, replacing prior hardcoded restrictions.

• Unified Observability: Total executions, status, history, and triggers are accessible to admins and authorized users within the enhanced IDP Run History.

Introducing the All-New Pipeline Activity View with a Cleaner, Faster Experience

We've redesigned the Pipeline Activity view to give you a cleaner, faster way to track and review pipeline runs.

Key Highlights:

• Cleaner Run History Table: Pipeline runs are now displayed in a structured table showing who triggered the run, run number, status, time taken, and last deployed timestamp, making it easy to scan across runs at a glance.

• At-a-Glance Status Indicators: Each run now shows a clear success/failure indicator alongside execution time and deployment timestamp, so you can quickly identify anomalies without digging into logs.

• Streamlined Navigation: The pipeline detail view is now organized into three focused tabs, Deployments, Workflow, and Parameters reducing noise and helping you get to the information you need faster. Read more here

Native Playwright Test Step for CI/CD Pipelines

A dedicated Playwright Test pipeline step has been introduced to simplify running Playwright test suites within CI/CD pipelines. Teams can now configure and execute Playwright tests directly in the pipeline without relying on custom scripts.

Key Highlights:

• Built-in Playwright Step: Users can add a Playwright step directly from the pipeline step to run automated browser tests as part of CI/CD workflows.

• Quick Test Configuration: Configure Playwright tool selection, code directory, Node dependency version, SCM settings, and custom command arguments (e.g., project, retries, headed mode) with built-in validation.

• Automated Execution & Reporting: The step execution logs in real time to the pipeline logs, automatically marks the step as pass or fail based on the test results, and saves the Playwright test report as a pipeline artifact. Read more here

Improved Tool Connection Health Alerts

Tool Connections provides alerts for failed or unhealthy integrations, helping users detect and resolve connection issues before they impact pipeline executions.

Key Highlights:

• Failure Notifications: Users receive email alerts when tool connections fail due to authentication issues or API errors.

• Detailed Alert Information: Notifications include the tool name, connection type, error details, and the last successful connection time.

• Configurable Alerts and Visibility: Alerts can be enabled or disabled per tool, notifications are sent to the tool owner and pipeline administrators, and a dashboard displays tool connection health status.

Enhanced PR Writeback for Terraform Output in GitHub PR Comments

PR Writeback includes an expanded Terraform Plan and Apply console output directly in GitHub Pull Request comments. This enables engineers to review infrastructure changes within the PR with greater visibility, reducing the need to switch to the Opsera console and improving the infrastructure review workflow.

Improved Console Log Copy and Download Functionality

Console logs support Copy and Download options, making it easier to capture and share logs for troubleshooting and incident analysis. Users can quickly copy log content or download log files without manually selecting large log outputs.

Key Highlights:

• Multiple Log Support: In pipelines with multiple log tabs (such as GHA), users can copy or download individual logs separately.

• Log Handling for Large Outputs: Logs can be copied or downloaded without manually selecting or scrolling through the entire log content.

Enhanced MCP Support for End-to-End Pipeline Lifecycle Operations

Opsera introduces enhanced MCP capabilities to support structured pipeline lifecycle management through MCP APIs. This enables AI assistants to interact with pipelines using defined operations, improving reliability and reducing dependency on iterative LLM prompts.

Key Highlights:

• Pipeline Lifecycle Management via MCP: Added support for core pipeline operations including Create, Clone, Update Configuration, Run, Stop, Reset, and Delete pipelines, enabling complete pipeline lifecycle management through MCP.

• Pipeline Execution and Control: Pipelines can be triggered, stopped, and reset via MCP, enabling automated execution and operational control without requiring UI interaction.

• Pipeline and Tool Metadata Retrieval: Introduced the ability to retrieve pipeline and tool configuration details by ID, allowing MCP workflows to dynamically reference existing configurations when creating or updating pipelines.

• Metrics and Reporting Integration: Pipelines created or executed through MCP are now reflected in platform metrics and reporting, enabling tracking of pipeline onboarding and operational usage over time.

Salesforce

Introducing Org Insights Dashboard for Salesforce Insights

Org Insights for Salesforce provides a unified analytics experience, giving engineering and release teams full visibility into Salesforce testing and deployment. By consolidating this data, teams can ship faster, catch issues earlier, and confidently maintain org quality.

Key Highlights

• Pipeline Health at a Glance

  • Track total pipelines, success rates, deployment vs. validation runs, and component counts at a glance.

  • View execution trends by success/failure or frequency, broken down by trigger type (Webhook, Scheduled, Manual)

  • Monitor rollback frequency over time, including External and Quick Deploy rollbacks

  • Drill into Pipeline Stages to understand stage-wise execution trends, average time, and distribution analytics

• Full Visibility into Every Deployment

  • Track total components deployed, unique components, profiles and permission sets, rollbacks, and external deployments

    • View component distribution by metadata type and deployment action (Added, Modified, Removed, Unmodified)

  • Analyze deployment trends over time and identify failure-prone components, most deployed components, and top failure reasons

  • Use Component Lookup to search any component and view its complete deployment history

• Test Quality, Coverage & Failures in One Place

  • Monitor test classes, methods, execution time, failure rate, and org-wide Apex coverage across all pipeline steps

  • Compare test runs against Apex deployments to catch gaps where code went out untested

  • Track coverage pass/fail trends over time

  • Identify top failing tests and lowest-coverage Apex classes before they impact production

• Org Security, Metadata & Platform Limits

  • View profile count, permission sets, and license usage by profile type

  • Track metadata types, component counts, and metadata trends over time

  • Understand active vs. inactive users and daily/weekly/monthly engagement patterns

  • Monitor real-time platform limit usage such as API calls, data storage, file storage, and async Apex calls Read more here

Enhanced Salesforce Cycle Time Insights

Salesforce Cycle Time Insights has been enhanced with additional execution analytics, improved visualizations, and expanded task and validation insights. These updates provide clearer visibility into development execution patterns, component activity, and validation outcomes to help teams better analyze Salesforce development cycle performance.

Key Highlights:

• Execution and Component Trends: Displays component retrieval activity and components processed per day with scatter plot visualizations of execution counts over time.

• Task Execution Analysis: Provides detailed task execution insights with linked task IDs, enhanced tooltips, improved execution tables, and searchable task data.

• Validation and Performance Metrics: Highlights PR validation activity, top users, top components, and component failure distribution to help teams track validation outcomes and identify performance patterns. Read more here

Ignore Whitespace Differences in Diff View

A capability is available in the diff viewer to hide whitespace differences during code comparison. This allows users to focus on meaningful code changes without being affected by formatting variations.

Key Highlights:

• Whitespace Toggle in Diff View: Users can now choose to hide or display whitespace differences directly within the diff screen powered by the Monaco editor.

• Cleaner Code Comparison: When enabled, the capability ignores whitespace changes such as spaces, tabs, and indentation differences, helping users focus on actual code changes.

• Optional and User-Controlled: The whitespace visibility can be toggled on or off, giving users flexibility when reviewing diffs. Read more here

Support for Salesforce Live Chat Agent Components in Salesforce Workflows

Opsera supports Salesforce Live Chat Agent metadata types, enabling consistent management across migration, version control, and deployment workflows.

• Metadata Types Supported

  • LiveChatAgentConfig

  • LiveChatButton

  • LiveChatDeployment

  • LiveChatSensitiveDataRule

• Workflow Support These metadata types are supported across Salesforce workflows, including Salesforce to Git Merge Sync, Git to Git Merge Sync, Bulk Migration, Pipeline Workflow, Jira Tagging, and Back Merge Flow.

• VS Code Plugin Support The Opsera VS Code plugin supports these metadata types for package generation. Read more here

Additional Capabilities

Enhanced Report View Controls for Salesforce Back Merge

The Salesforce Back Merge task supports zoom-in, zoom-out, and reset controls in the expanded flow view, allowing users to adjust visualization scale for better readability and quickly restore the default layout during analysis.

DataOps

Streamline Bundle Resource YAML Updates from Git with DataOps Codegen

DataOps Codegen supports fetching existing bundle resource YAML files from Git, allowing users to view and update previously generated bundle assets. Users can modify these assets and commit the updated bundle configurations back to Git.

Key Highlights:

• Select Bundle Files: Users can browse and select bundle resource YAML files from the connected Git repository for management within Codegen.

• Edit Bundle Assets: Fetched bundle resource files can be modified directly within the Codegen interface.

• Review and Commit Changes: Users can review modifications and commit updated bundle resource YAML files to Git to persist the changes.