Release Update 03/21/2026

Unified Insights

Enhanced Date Filtering for Quality Posture Dashboards

To offer more precise time-series analysis, a Custom Date Range filter is available on the Quality Posture Dashboards. This allows performance measurement over custom periods by selecting exact start and end dates, moving beyond full-month restrictions.

Key Highlight:

• Granular Date Selection: Replaces the restricted "Custom Month" picker with a flexible Calendar Tool, allowing you to define any specific window for your data analysis. Read more here

Introducing Expandable Sprint Leadership Report for Global and Team Transparency

The Sprint Leadership Table features a Expand capability, providing a single-action view of all nested data. This eliminates manual clicks, offering complete visibility to audit and compare performance across individual teams.

Key Highlights:

• One-Click Hierarchy Expansion: Expand Icon in the table header that opens all subcategories simultaneously.

• Full-Screen Layout Transition: When the expand option is clicked, the leadership table opens in a dedicated overlay layout, providing a wider canvas to view metrics without horizontal or vertical scrolling. Read more here

GitHub Issues Integration for DORA Metrics and Mapping

GitHub Issues Mapping is supported for Cycle Time For Changes, Mean Time to Resolution, and Changes Failure Rate KPIs, offering more accurate delivery tracking. The base formula for these KPIs remains unchanged and uses standard industry definitions.

Key Highlights:

• Integrated Tool Filtering: Includes GitHub Issues as a selectable option in the global tool filters for the DORA dashboard, enabling side-by-side comparisons with other integrated tools.

• GitHub Project Mapping: users can select a specific GitHub Project as the primary data source for DORA calculations, ensuring metrics are scoped to the correct team or product. Read more here

API Integration for GitHub Copilot Premium Request Visibility

Opsera uses the dedicated GitHub Premium Request APIs to enable precise cost management and usage tracking. This provides real-time data on advanced AI consumption directly in the Copilot Dashboard, helping users monitor budget utilization for advanced models and agentic features.

Key Highlights:

• API-Driven Billing Reports: Consumes data from the GitHub billing endpoints to provide a granular breakdown of Copilot Premium Request usage across the entire organization.

• SKU-Specific Tracking: Displays usage metrics attributed to specific premium SKUs, including Copilot Chat, CLI, Code Review, and Coding Agents, allowing teams to pinpoint which features drive costs.

• Quota and Allowance Monitoring: Visualizes current consumption against your plan’s monthly premium request allowance, making it easy to see when a team is approaching its limit.

• Overage and Budget Visibility: Reports on billed overages and remaining credits, helping leadership manage spending limits and avoid unexpected billing cycles for advanced AI tasks.

• Unified KPI Support: Syncs these data points with existing Copilot KPIs, such as total requests, model multipliers, and per-user consumption trends. Read more here

Introducing Average User Engagement Metric for Snaplogic Dashboards

To provide users with clearer insights into team productivity, The Average User Engagement tile is added to the User Activity Tab within the Snaplogic dashboard. This helps leads and admins identify how deeply team members are interacting with the platform by showing a calculated engagement score for every active user within a selected time frame.

Key Highlights:

• Average Engagement Score Tile: Displays a high-level metric in the User Activity representing the average interaction level of all active users, providing a quick pulse check on platform adoption.

• Engagement Scoring Logic: Measures the specific activity levels for each user and aggregates these scores into a single team-wide engagement metric. Read more here

Salesforce

Enhanced Salesforce User Story Task Integration for Commit Messages

The Salesforce User Story Task Integration has been enhanced to include Jira ticket references in commit messages during task execution. Users can automatically include selected Jira tickets in commit messages without manual input. This ensures consistent traceability between commits and associated Jira work items.

Key Highlights:

• Default commit message: Populates the commit message with the selected Jira ticket during task execution when no message is provided.

• Multiple Jira references: Includes all associated Jira stories in the commit message for Git-to-Git workflows when multiple tickets are selected. Read more here

Capability to Restrict PR Merge in Salesforce Back Merge Sync

Salesforce Back Merge Sync introduces the Restrict PR Merge toggle to control pull request merge behavior for Git branch targets. Users can configure whether a pull request is merged automatically or created for manual merge during back merge execution. This enables controlled promotion flows where manual validation is required before merging.

Key Highlights:

• Manual merge behavior: When the Restrict PR Merge toggle is enabled, execution stops after pull request creation and requires manual merge.

• Automatic merge behavior: When the Restrict PR Merge toggle is disabled, the pull request is merged automatically if there are no conflicts.

• Step completion: The Pull request creation step is marked as successful in both scenarios. Read more here

Support to De-link Component Mapping in User Story Insights

The User Story Insights dashboard introduces the capability to de-link component mappings from Jira stories for a selected target branch. Users can remove existing mappings directly from the dashboard. This provides better control over component associations and ensures accurate mapping management.

Key Highlights:

• Branch-specific action: Applies de-linking only to the selected target branch without impacting other branch mappings.

• Audit tracking: Captures audit entries for de-link actions, consistent with other mapping operations. Read more here

Introducing Smarter Branch Control for Salesforce Pipelines

Salesforce pipelines support branch-specific triggering directly from the Start of Workflow step configuration. This helps ensure pipelines run only when events are received for relevant branches that align with your development workflows.

When a webhook push event is received, the pipeline evaluates the incoming branch against the configured branch name or branch pattern. A pipeline run is initiated only when a match is found.

Key Highlights:

• Precise pipeline triggering: Pipelines execute only for the branch or branch patterns defined in the Start of Workflow configuration.

• Support for branch and branch patterns: You can configure either a single branch or a branch pattern. Example:

  • main triggers only for the main branch

  • release* triggers for branches such as release, release-1.0, and release_candidate

  • feature* triggers for branches such as feature-login, feature/api-update, and featureUI This allows teams to support both fixed branches and multiple dynamic branches without creating separate pipeline configurations.

• Branch-aware package creation: The package XML is generated using the pushed branch that matches the configured branch or branch pattern.

• Default behavior: If no branch pattern is configured, the pipeline triggers based on events from the configured primary branch. Read more here

Support for Agentforce Metadata Components

Opsera supports Agentforce metadata types, enabling consistent management across migration, version control, and deployment workflows within pipelines using Job Engine.

Metadata Types Supported:

• AIApplication

• AIApplicationConfig

• AiEvaluationDefinition

• AIScoringModelDefinition

• AIUsecaseDefinition Read more here

Platform

Enhanced User Role Management and Pipeline Control

This capability strengthens access control, improves user visibility, and enables safer delegation by requiring explicit role selection, making all users (including Guests) auditable, and allowing Managers to control pipeline stages without full admin access.

Key Highlights:

• Mandatory Role Selection: Users must select a role during registration; no default assignments

• Guest User Visibility: Guest users are now visible and auditable in the system

• Unified Role Display: Site roles are shown directly in the main Users list

Cross-Account IAM Role Support for AWS Deployment Steps

This feature enables secure deployments across AWS accounts by allowing pipeline steps to assume IAM roles in target accounts. It simplifies multi-account deployment workflows while eliminating the need to manage account-specific credentials.

Key Highlights:

• Multi-Account Deployments: Run deployments across multiple AWS accounts from a single pipeline using role-based access.

• Enhanced Security: Leverages temporary credentials via IAM role assumption, reducing reliance on long-lived access keys.

• Simplified Operations: Eliminates the need for maintaining separate credentials or duplicating configurations for each account.

Case Sensitivity for Site Roles in the User Management APIs

Site roles in the user management APIs are updated to use case-sensitive values and must be passed using the supported role names during user creation API requests. Users must provide the correct role names with exact case sensitivity to ensure successful role assignment. Supported Site Role values:

• administrator

• powerUser

• user

• auditor

• securityManager

• guest Read more here