Release Update April 2025
Salesforce
Redesigned Merge Sync and Profile Deployment Experience
A new, unified task wizard has been built to replace task execution workflows for Salesforce to Git, Git to Git, and Profile Compare and Deploy tasks. This user-centric redesign focuses on simplifying complex tasks with intuitive guidance
Upon task execution, users get a navigation with pre-execution configuration validation steps, with precise control over metadata components selection.
The Diff screen clearly highlights differences between code versions, letting you resolve conflicts (e.g., overwrite, keep, or edit changes) with confidence. For profiles and permission sets, the task only updates permissions tied to the components you select to prevent any accidental over-access. Before finalizing, a Checkpoint Screen ensures critical actions are confirmed, and a Summary Page displays exactly what will change, including impacted components and dependencies.
Together, the enhanced wizard setup accelerates task setup for teams to align with Agile workflows, all while reducing manual effort and ensuring metadata integrity.
Enhanced Pull Request Management in Jira Integration
The capability to review and update Pull Requests has been extended for the merge synchronization workflows for repositories integrated with Jira. This allows teams reusing existing PRs efficiently to reduce redundancy and accelerate development cycles.
When configuring Salesforce to Git or Git to Git Merge Sync Tasks with Jira configuration, users can select PRs aligned with their Jira tickets or target branches. Updates can be committed directly to the PR's source branch after being reviewed in the diff editor interface.
Please note that the Profiles included in the PR are handled carefully by only including permissions tied to selected components and excluding unrelated metadata. Additionally, object dependencies are excluded from deployments unless explicitly selected. Upon successful task completion, the linked Jira ticket is auto-updated with task details.
Introducing Automated Failure Recovery for Salesforce Pipelines
Opsera has added a new feature for Salesforce pipelines to consider components from the failed run.Now, if a pipeline fails due to webhooks or scheduled tasks, it can restart using commits from the last successful update, with no manual intervention needed.This ensures all the components are considered in consecutive commits without missing out on any components.
Admins can turn on a new setting called “Enable Pipeline Execution From Last Failed Commits” in the pipeline settings. This configures the Pipelines to reuse the last stable version of the code automatically. For scheduled runs, the Pipeline uses the earliest time between the last successful run and the scheduled task to find the right set of commits . For webhook runs, it looks for changes made after the last successful run.
This makes redeployments quick, consistent, and easy to track, while lowering the chance of errors.
Simplified Task Execution from Salesforce Landing Page
The Critical task controls like starting and stopping executions have been simplified with dedicated buttons added directly to the Salesforce Landing Page. This replaces the need to navigate through the specific Pipeline workflow thereby reducing clicks.Centralizing controls and surfacing real-time insights enables teams to have a cleaner interface designed for high-impact Salesforce management.
Please note that the Start button activates only when tasks are idle, preventing duplicate runs.
Enhanced Salesforce PR Validation for Non-Salesforce Component Changes
An enhancement is made to automatically approve Salesforce PR validations when pull requests contain only non-Salesforce components. Previously, such PRs were flagged as failed due to the absence of Salesforce metadata requiring package.xml generation, blocking the Merge Pull Request option.
With this improvement, PRs that consist of both Salesforce and non-Salesforce files, will be validated by Opsera without hindrance. Conversely, PRs that contain Salesforce components will still be subject to the existing validation checks to ensure compliance.
Platform
Enhanced User Search for Groups & Site Role and User Management
A new search functionality has been implemented on the Groups, Site Role, and User Management pages. The dedicated search bar will be located at the top of the user list enabling searches by name, email address, or username.
This enhancement simplifies the management of large user bases by enabling administrators to quickly and easily locate specific individuals within extensive lists.
Enhanced Pipeline Insights with Open Issues Tracking in GitCustodian Summary Reports
The GitCustodian pipeline summary report now displays openIssues for enhanced visibility into unresolved issues impacting workflows.This addition of openIssues supports better decision-making by highlighting risks and fostering accountability while integrating smoothly into existing workflows.
Enhanced Filtering for Pipeline Activity Logs
Two new filters have been introduced to the Pipeline Activity Log table, aimed at improving the efficiency of troubleshooting, auditing, and analysis for users.
The new filters include options to sort by Action (such as "approve step," "status check," or "report") and by the Pipeline’s Step Name. This addition complements the existing filters that focus on Run Count and utilize a Search Bar to analyze specific Pipeline progress.
Policy Management Enhancements
The Policies configuration has been relocated to the left navigation bar for quicker access, replacing its previous placement within the "Settings" configuration.
Opsera has introduced Role-Based Access Control (RBAC) specifically designed for policy management. This allows organizations to customize access rights to various policies, enhancing their overall access control mechanisms. Users will gain access to the Policies section if they either possess explicit RBAC permissions for at least one policy or inherit such permissions through their designated site role.
In terms of default privileges:
Administrators retain full read/write/delete privileges.
Power Users, Security Managers, and Auditors have read-only access.
Please note that the Users and Guests are excluded unless granted RBAC permissions.
Enhanced GitHub Insights Tool Configuration with Admin-Controlled Data Ingest
Opsera's GitHub Insights Tool Registry configuration has been redesigned to provide granular control over data ingestion.
The data ingest controls have been integrated into the Connections Tab replacing the existing Data Ingest tab. Admins can now enable/disable data collection for Copilot reports, DevEx (PRs/commits), Actions, and Security with a single click, either per organization or in bulk via column header checkboxes.
This unified interface reduces complexity, accelerates setup, and ensures consistency across all data types, while restricting configuration access to authorized tool admins for enhanced security. Admins gain granular control without tab-hopping, reducing errors and enabling faster compliance with organizational data policies.
SDLC
Enhanced Branch Flexibility for Jenkins to GHA Pipeline Migration
The Pipeline Migration workflow between Jenkins-to-GitHub Actions allows teams to configure their pipeline to select source code from any branch, not just the default branch. This capability significantly improves flexibility in managing code migrations.
A dropdown menu for target branches has been introduced in the migration configuration that displays all branches with valid source references. This allows users to easily migrate pipelines linked to feature branches, hotfixes, or experimental code without needing to manually switch branches or reconfigure repositories. Consequently, this update reduces the likelihood of errors and streamlines the process of migrating across various branches.
Unified Insights
New Capabilities for GitHub Copilot Dashboard
Copilot dashboard's new features include:
View Developer Productivity Report in Dashboard’s Base View
The Developer Productivity Report, including monthly productivity trends and team-level drill-downs, is now permanently visible in the dashboard’s base view, eliminating the need to navigate away for analysis. Teams can instantly review language-specific contributions and productivity patterns directly from the default interface, accelerating data-driven decisions.
Rename KPI Widgets
The Copilot Dashboard allows Admins to rename KPI widgets to better reflect team-specific terminology, enabling clearer communication with stakeholders while staying aligned with organizational processes.
Custom names can be applied dashboard-wide, ensuring real-time consistency for all users across the Developer Productivity and Copilot Usage Reports. To maintain governance, renaming permissions are exclusive to Admins, preventing unauthorized edits.
Exclude Languages in Developer Productivity Report
A language exclusion filter allows Admins to refine productivity metrics by omitting specific programming languages. In the User Settings Panel, Admins can use a multi-select dropdown to exclude languages, with changes instantly recalculating metrics and updating visualizations. For broader adjustments, an “All” option or multi-selection can be performed to exclude multiple languages in one action.
Together, these upgrades empower teams to tailor data views, improve report accuracy, and align insights with organizational processes seamlessly.
Additional Enhancements
Enhancements to Twistlock Vulnerability KPI
The Twistlock Security overview chart view now sorts projects in descending order by the total number of issues to improve the visibility of projects with the highest issue counts.
Last updated
Was this helpful?