Version 6.1.0

Features

1. JIRA Credential Validation & Proxy Configuration

• Introduced a Validate option during JIRA credential registration for Basic Authentication, OAuth, and Bearer Token methods. This enables validation of JIRA credentials to ensure successful connectivity using any of the supported authentication types.
• Enhanced existing proxy capabilities by adding support for SAP Cloud Connector. This enables secure connectivity between ReleaseOwl and on-premise JIRA instances, allowing access to JIRA systems within the client network without exposing them externally.

2. New Pipeline Tasks in Release Pipelines

Introduced new pipeline tasks to enhance governance, validation, and control during the release process.

Newly Added Tasks:

• Checklist Task
  • Introduced Checklist Task in release pipelines to enable execution of structured pre-release validation and compliance checks.
  • Allows teams to define and verify mandatory steps, approvals, and conditions that must be completed prior to deployment.
  • Ensures adherence to organizational standards and release governance by enforcing checklist-driven validations.
  • Reduces the risk of missed steps and improves overall release quality by confirming readiness before progressing further in the pipeline.

  
• Once a Checklist Task is added to a User Story and promoted, the assigned user can access it from the My Tasks section via the Approve / Reject action.
• Within the task, all checklist items are displayed, including mandatory items marked with a star (★). Users can upload required files, mark items as done, and provide comments as needed.

• After performing Approve or Reject, the executed checklist details can be viewed in the Pipeline Activity section.

• Introduced a Branch Merge Task as part of the release pipeline workflow to enable merging of changes from one branch to another using supported source control systems such as Git.

• In case of merge conflicts, the conflicts are surfaced at the User Story level, allowing users to review and resolve them as part of the workflow.

User Story Field Task

• Introduced a new pipeline task User Story Field Task to enable dynamic synchronization of user story fields with integrated ALM systems such as JIRA.
• As part of the ALM integration, user story metadata (fields) are automatically fetched from the external system and made available within ReleaseOwl. This task ensures that these fields are programmatically updated and aligned during pipeline execution.
• The task operates by:
  • Retrieving configured user story fields from the integrated ALM system
  • Mapping and updating those fields within the ReleaseOwl user story context
• Enables better traceability and data integrity by ensuring that critical fields (such as status, metadata, or custom fields) remain up to date throughout the release lifecycle.
• Improves overall pipeline automation by incorporating field-level updates as a controlled task, ensuring that user story data is accurate before progressing to subsequent stages.

3. SAP CPI Environment – Mock Prefix Configuration

• Introduced Mock Artifacts Prefix in SAP CPI Environment configuration, which becomes available when Test Automation is enabled.
• Allows users to define a custom prefix value that is used to dynamically bind mock endpoints during test execution.
• When a Mock Prefix is specified:
  • Relevant endpoints are automatically mapped to their corresponding mock services
  • Ensures that test cases are executed against mocked integrations instead of actual backend services

  

4. Origin Key – SAP Passport & SAP Cloud Identity Services

• Introduced Origin Key support for both SAP Passport and SAP Cloud Identity Services (Identity Authentication) to enhance authentication handling and request traceability.
• For SAP Cloud Identity Services (OIDC-based Web Authentication), users can retrieve the generated Origin Key from the Trust Configuration and configure it in ReleaseOwl after saving the credential.
• For SAP Passport, the default Identity Provider Origin Key available in SAP BTP Trust Configuration can be used.
• This ensures consistent and secure integration with authentication providers across different credential types.

Improvements

1. Integration Advisor – Tab-wise Segregation of Integration Advisor Artifacts

• Introduced separate tabs (MAG and MIG) for Integration Advisor artifacts.
• Enables users to sync individual artifact versions more efficiently.
• Enhances usability by providing a structured and organized view of artifact.

2. API Management – Sync & Configuration Improvements

In this release, we have introduced several enhancements to improve the usability and flexibility of API Management synchronization and configuration in ReleaseOwl.

Key Updates:

• Added support for API Provider and API Product as part of the API Management synchronization and configuration process.
• Introduced separate tabs for different API artifacts to clearly distinguish each component, enabling users to easily identify, navigate, and manage specific artifacts.
• Enabled individual synchronization of API artifacts, allowing users to sync specific components and fetch the latest versions from the registered SAP API Management environment.

3. My Tasks – Reference ID Navigation

In this release, we have enhanced the navigation experience in the My Tasks section within release pipeline tasks by introducing clickable Reference IDs.

• Tasks originating from User Story, Release Package, and Transport Management (with default pipeline configuration) are now traceable.
• Clicking the Reference ID redirects users to the respective source screens (User Story Edit / Release Package Edit / Transport Edit).
• Improves navigation, traceability, and overall user experience.

4. CPI Alerts – Actionable Insights & Navigation

• Enhanced CPI Alerts with actionable operations available directly from the alert details panel for alerts in Open/Failed status.
• Introduced Raise Defect action:
  • Allows users to create a defect directly from the alert context
  • Integrates with SAP Cloud ALM for defect registration
  • Enables seamless transition from monitoring to defect tracking without manual navigation

  
• Introduced Code Change option:

  • Provides access to analyze changes related to the impacted artifact
  • Helps in identifying differences between versions contributing to the failure
  • Supports faster root cause analysis by linking alerts with recent changes

  

5. Role-Based Access for Import Settings

• Updated access control for Import Settings in Integration Advisor artifacts.
• Previously, Import Settings were available at the Administration level. This has now been enhanced to follow a role-based access control mechanism.
• Access to Import Settings is now governed through User Management → Roles configuration:
  • Administrators must assign appropriate roles to users in the Manage Users section
  • Within the assigned role, the Import Settings permission must be explicitly enabled under Role Actions
• Only users with the required role permissions will be able to view and access the Import Settings option for the artifacts.
• Additionally, Import Settings can now be enabled and accessed during the In-Progress stage, allowing users to perform import operations earlier in the lifecycle.

6. Sync History & Validation Report – Integration Advisor

• Enhanced Sync History in both API Management and Integration Advisor to include additional artifact-level details.
• Added new columns:
  • Artifact Name
  • Artifact Type
• When a single artifact is synchronized, the Sync History displays the corresponding artifact name and type, providing clear visibility into the synced item.
• When synchronization is performed based on artifact type (bulk/type-based sync), the system represents the entry with a generic indicator (e.g., ‘*’) instead of a specific artifact name.
• Improves traceability and auditability by clearly distinguishing between individual artifact sync operations and type-based sync actions
• Introduced Validation Report for Integration Advisor, providing detailed insights into the outcome of synchronization operations.
  • Enables users to review validation results and identify issues at the artifact level
  • Improves visibility into sync execution and artifact consistency