Release Update 01/22/2026
Salesforce
Introducing Back Merge Workflow for a Controlled Sync Across Salesforce and Git


Opsera introduces a Back Merge capability to merge changes from a higher environment back down into a lower development branch or Sandbox. With a visual flow setup, teams can keep environments in sync and ensure that hotfixes and changes made in one place are seamlessly synced across all downstream environments.
Key Highlights:
Source-to-Target Synchronization: The merge captures changes from a selected source (Salesforce org or Git branch) and syncs them to one or more target orgs or branches, keeping all environments aligned with the latest approved updates.
Visual Flow Configuration: The merge flow is set up using an intuitive visual canvas that clearly shows source-to-target relationships. Targets can run in parallel or in sequence, offering flexibility with full control over execution.

Automated Execution with Clear Status: Each run displays real-time status for every target, including successful merges, no-change results, PR creation and merge status, or deployment failures.
Detailed Reporting: Comprehensive reports are generated for every execution, including deployment details, package.xml visibility, component-level results, and linked PRs.

Faster Access and Stronger Governance for Salesforce Dashboards
Teams can quickly access the Salesforce dashboards they use most while gaining clear visibility into dashboard activity.



Key Highlights:
Favourite Dashboards for Quick Access: Teams can mark frequently used dashboards as Favourites, making it easy to open key dashboards without searching through long lists.
Centralized Favourites View: A dedicated Favourites menu brings all marked dashboards into one place, improving navigation efficiency and user productivity.
Audit Trail for Transparency and Compliance: Teams can view an Audit Trail for each dashboard, providing visibility into dashboard activity and supporting traceability, compliance, and operational oversight.
Platform
Unified Multi-Team Incident Management with Opsgenie



Opsera integrates Opsgenie into the IDP catalog, allowing teams to manage on-call schedules, paging, and escalations using their preferred incident management platform. This enables flexible, multi-team incident response while maintaining a consistent operational experience across the organization.
Key Highlights:
Opsgenie Service in the IDP Catalog: Opsgenie is available as a native service tile in the IDP module, allowing teams to select the incident management platform that best aligns with their workflows.
Simple and Secure Integration Setup: The integration is configured using required connection details such as the Opsgenie API key and instance URL, ensuring secure and reliable communication.
Multi-Team and Multi-User Paging: Teams can configure paging for multiple schedules and users, enabling accurate incident routing across teams through centralized IDP configuration.
Smarter Chat History Management for Faster Knowledge Retrieval


Key Highlights:
Chat History Viewing and Search: Users can view past chat conversations and search chat history using the search bar to quickly locate previous discussions.
Easy Access via History Panel: Chats are accessible through the dedicated Chat History panel, allowing users to browse and reopen prior conversations with ease.
In-Chat Feedback Submission: Users can share feedback directly from the chat interface using the feedback option, helping improve the experience.
Introducing Opsera MCP: Unified Automation & Insights Directly in Your IDE
Opsera MCP (Model Context Protocol) Server brings Opsera’s automation power straight into your development environment. Compatible with IDEs like Cursor and VS Code, the MCP Server acts as a secure proxy for Opsera’s 50+ public APIs and lets developers use natural language prompts to access functionality.
Key Highlights:
Build Pipelines with Natural Language: Developers can create complex SDLC, Salesforce, or AI/ML pipelines using simple prompts, eliminating repetitive configuration steps and accelerating workflow setup.
Seamless IDE Experience: Run, monitor, and manage pipelines and dashboards directly within your IDE (e.g., Cursor or VS Code), enabling end-to-end workflow automation without context switching.
Additional Capability
Improved Clarity in Jira Pipeline Alerts
Jira pipeline alert notifications now display the exact configured names of the pipeline and steps, instead of numeric IDs. This ensures alerts clearly reflect the true source of execution and are easier to understand and act on, especially in environments with multiple pipelines and complex workflows.

Unified Insights
Introducing Active PR Time Metrics for Pull Request Statistics KPI


Teams now have a clearer way to measure pull request cycle time and gain deeper insights into the overall pipeline efficiency
Key Highlights
New Active PR Time Metric: Active PR Time column in the Pull Request Statistics table shows how long a PR was actively worked on after approval. Calculation: Active PR Time = Merge Time − Approval Time − Created Time
Flexible PR Cycle Time Interpretation: Teams can now distinguish between time from PR creation to first approval and the time from approval to merge.
Introducing New Insights for the Windsurf Dashboard


Users can view a set of new KPIs and reports on the Windsurf dashboard that provide actionable insights into user adoption, developer activity, code impact, and AI-assisted productivity.
New Metrics Added:
Total Licensed Users: The total number of people who have a valid license to use Windsurf.
Active Users: Licensed users who actually used Windsurf within the selected date range.
User Adoption Rate: The percentage of licensed users who were active during the selected period.
Developer Activity: How often developers are engaging with the tool.
Adoption: How widely Windsurf features are being used across the user base.
Suggestion Retention Rate: How often suggestions are repeatedly used or kept over time.
Windsurf Contribution Report: A summary view showing usage and activity metrics (like how much each user contributes).
Visualizations & Export Options:
Line Graphs are improved for adoption, impact, acceptance rate, and retention trends.
KPI tables are provided with Export for usage metrics and contribution reports.
Enhanced Filtering All dashboard views now support advanced filters such as Geography and Vendor.
Introducing Aggregated Sprint Velocity View for Multi-Team Offerings
Users can see a Unified Sprint Velocity View that shows delivery performance across teams within an offering. The chart compares committed vs completed story points for the most recent completed sprints, regardless of individual team schedules.

Key Highlights
Configurable Sprint Range: Users can choose the last 5–10 completed sprints (N), where N is based on sprint count, not calendar dates.
Multi-Team Aggregation: For a selected offering, the chart gathers each team’s most recent completed sprints and totals committed vs completed story points across all teams.
Sprint Alignment by Order: Sprints are shown from most recent to oldest based on sequence, not actual dates, making comparisons clearer across teams with different cadences.
Last updated

