C³F – Cross Connector Features
Deliver the SAP Cloud ALM release scope in Jira
Features and Jira issues in sync both ways.
The challenge
Scope in Cloud ALM, delivery in Jira
You manage the scope of your SAP releases as features in SAP Cloud ALM. Your delivery teams, however, implement it in Jira. Feature and Jira issue do not know each other, and the deployment status is missing in Jira.
So the lifecycle is retyped by hand, owners appear twice in both systems, and at worst something goes live that was never approved.
Unclear scope
Releases slip because nobody knows for sure what belongs to them.
Double maintenance
Status and owners are maintained in two systems.
No audit trail
End-to-end traceability between feature and delivery is missing.
The solution
One release scope, two systems
C³F connects the features from the implementation area of SAP Cloud ALM with Jira. Features and Jira issues are created, updated and closed in both directions.
SAP Cloud ALM stays the system of record for scope, lifecycle and deployment status. Only your Cloud ALM users set Ready for Production.
Both directions
Features and issues are created and kept current, wherever someone starts.
One click there and back
The feature holds the URL of the Jira issue, and a panel in the issue shows the sync status.
Your configuration
Several profiles per Jira project and issue type, with flexible field mappings.
How it works
From feature to delivery
1
Feature in Cloud ALM
The release scope starts as a feature in SAP Cloud ALM, or a team creates the issue in Jira first.
2
Create the counterpart
C³F creates the matching counterpart in the other system and links both.
3
Deliver in Jira
Delivery teams work in the Jira issue. Owners are matched by email address.
4
Align the status
C³F maps the status path from specification to confirmed delivery.
5
Trace it
An activity tab in the issue shows the log of every synchronisation.
Technology: public SAP Cloud ALM REST APIs, authentication via OAuth 2.0 client credentials, changes arrive by webhook. SAP Cloud ALM is SaaS, so you install no ABAP add-on and run no SAP backend.
After 2027
The path from Solution Manager to SAP Cloud ALM
According to SAP, mainstream maintenance for Solution Manager ends in 2027 (SAP Support). SAP Cloud ALM is the successor, but it comes without a Jira connection.
The C³ suite closes this gap. Your teams keep working in Jira, and SAP Cloud ALM stays the system of record. Secure the Solution Manager history beforehand with CA1 and CA2.
More on the end of Solution Manager: What to do now →
At a glance
Technology, trial and price
| Jira | Jira Cloud, as a Forge app without a maintenance window |
| SAP | SAP Cloud ALM, implementation area (features) |
| Direction | Both ways: create, update, close |
| Trial | 30 days free of charge, with technical support from Cross ALM |
| Price | Free in Jira Cloud for up to 10 users, priced by user count above that. Current prices on the Marketplace |
Price for your team
Atlassian Marketplace prices in US dollars, excluding taxes. As of 19 Nov 2026.
Background
Further reading
Product
C³B for project tasks
All SAP Cloud ALM task types with assignee and status in Jira.
Product
C³O for operations
Alerts from SAP Cloud ALM as Jira issues, with closure reported back.
Consulting
Implementing SAP Cloud ALM
How Cross ALM supports your SAP Cloud ALM implementation.
Vendor
Developed by Cross ALM
Cross ALM develops C³F in-house and supports implementation and operation. Since 2015, the team has connected SAP processes with Atlassian and ServiceNow tools.

Atlassian Gold Solution Partner
Rising Star EMEA Partner of the Year 2022, with the Service Management Specialization.

SAP Silver Partner
Focus on application lifecycle management, from planning to operation.

One point of contact
Product, implementation and support from one source, with more than 25 people in Berlin.
Get started
Three steps to your pilot
Before you decide, you see C³F in your own landscape.
1 · Conversation
You describe your system landscape and requirements and see C³F in a demo based on your case.
2 · Pilot project
For 30 days you run a free licence in your landscape, with technical support from Cross ALM.
3 · Decision
Together you review whether the pilot delivered the expected value.
FAQ
What to know about C³F
Do we need an ABAP add-on?
No. C³F runs as a Forge app in Jira Cloud. SAP Cloud ALM is SaaS, so nothing is installed in SAP.
Who sets Ready for Production?
Still only your users in SAP Cloud ALM. C³F reflects the status but does not decide it.
Does C³F work with Jira Data Center?
C³F is built for Jira Cloud.
What does C³F cost?
In Jira Cloud, C³F is free for up to 10 users. Above that, the price depends on the number of Jira users; from the 101st user on, each additional user costs USD 0.01 per month. The price calculator above shows the amount for your team.
From the end of SolMan in 2027 to an agentic tool chain for SAP landscapes
How SAP teams plan the move and connect SAP, Jira and ServiceNow into one tool chain.
Contact
Let’s talk about your project
Tell us briefly what it is about, and you will hear from us personally.

What happens when you get in touch:
- A consultant gets back to you and clarifies your requirements
- Together with you, we analyse your processes and systems
- You receive a proposal for the next steps
You are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationPrefer to get in touch directly? Email solutions@crossalm.com or call +49 30 398 36 112.
