CrossConnector to SAP Cloud ALM Features (C³F) for Jira

by Cross ALM GmbH

works with Jira Cloud

OVERALL RATINGS
INSTALLS
SUPPORT: Partner Supported

Showing details for Cloud

Overview

Reviews

Pricing

Privacy & Security

Support

Installation

Similar Apps

New

Key highlights of the appLink SAP Cloud ALM Features with Jira automatically - delivery teams work in Jira while CALM stays the system of record for scope

More details

Cross Connector for SAP Cloud ALM Features is part of the Cross Connector product family, connecting SAP landscapes with Jira Cloud. It is built for SAP Cloud ALM Implementation teams that need auditable, bidirectional sync between CALM Features and Jira work items.

Language support: English (admin configuration, issue panel, and activity log). Status mappings use Jira status IDs, so the app works on international Jira sites regardless of locale.

Built on Atlassian Forge: OAuth-secured CALM API access, optional inbound webhook authentication, loop prevention, per-issue sync history, and Marketplace licensing.

Enterprise capabilities include multiple configuration profiles, profile export/import, scoped user mapping (CALM email to Jira assignee), and admin diagnostics.

Requires your own SAP Cloud ALM subscription plus customer-side CALM and SAP BTP setup. Documentation is linked from this listing. For CALM Tasks sync, see the separate Cross Connector Tasks app.

Resources

App documentation
Comprehensive set of documentation from the partner on how this app works

Privacy and Security

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Integration permissions

CrossConnector to SAP Cloud ALM Features (C³F) for Jira integrates with your Atlassian app

Version information

Version 7.4.0•for Jira Cloud

Release date: Aug 4th 2026
Summary: Minor version update
Details: Added a Resync action on the issue panel so users can retry outbound feature create when status is Failed or Not yet synced. Already-synced issues are blocked to avoid duplicates.
Resync respects the same outbound gates as automatic sync: configured create trigger status and sync-condition field must be met before create runs.
Outbound user mapping can now be configured (including create/update) so Jira assignees map to SAP Cloud ALM, in the desired way.
Payment model: Paid via Atlassian
License type: Atlassian Closed-Source