2026-04-07

—

2.4.2

Jump-in URL — placeholders + admin UI

Jump-in URL: Optional placeholders in the connection profile (#GUID#, #OBJECT_ID#, #OBJECT_ID_NO_ZEROS#, #GUID_NODASH#, #JIRA_KEY#) are replaced per synchronized issue. If the Jump-in field contains any of these tokens, the expanded value is the complete link shown to users (SAP’s per-ticket path from the API is not appended). Without placeholders, behaviour is unchanged (Jump-in or SolMan URL as base, plus SAP’s stored path). Admin UI: Long Jump-in help text is in a compact, collapsible grey panel. Platform (Marketplace): Jira Data Center 10.3.0 – 10.7.4.

2026-03-11

2.7.1 — SM line; FB line

—

SAP 2.7.1 — HTML texts, IMG

Builds on the 2.7.0 delivery stack. Convert ticket texts to HTML (several incremental corrections). IMG customizing updates for CC4 (standard + enhancement). Order imports through your usual SAP / Cross ALM process.

2026-02-25

—

2.4.1

Minor improvements — SAP attributes rendering + JQL

SAP Data display: When SAP attributes were first filled on an issue, the “SAP Data” block could appear in the wrong sections (e.g. Attachments, Activity). It now appears only in Cross Connector – Details, including immediately after the first fill, without reloading the page. JQL: key in cc4IssuesWithSyncStatusFailed() lists issues whose latest sync attempt failed. Platform (Marketplace): Jira Data Center 10.3.0 – 10.7.4.

2026-02-19

—

2.4.0

New features — JQL for SAP / Solution Manager + Project Bulk Sync

JQL: Search by SolMan link and SAP data without custom fields, e.g. cc4SyncedWithSolMan(), cc4NotSyncedWithSolMan(), cc4IssuesWithSolmanId("id"), cc4IssuesWithSolmanGuid("guid"), cc4IssuesWithSapAttribute("attr", "value") (Advanced Search / JQL, e.g. key in cc4SyncedWithSolMan()). Project Bulk Sync: Jira → Add-ons → Project Bulk Sync — bulk resync failed tickets per project. Platform: Jira Data Center 10.3.0 – 10.7.4.

2026-02-03

2.7.0 — SM line; FB line

—

SAP 2.7.0 — sync, JSON, attachments, REST

Builds on the 2.6.4 delivery stack. Description and priority transfer fixes. Attachment handling: conversion fixes and proxy support when reading attachments. Issue links in delta mode. Enqueue handling (commit work and wait). Fewer duplicate transaction creations; better detection when objects are created in parallel. Documentation for logical keys. JSON pipeline refactored with a path to restore older behaviour where needed. Additional value help values. HTML text conversion; REST improvements. Create scope performance improved (Focused Build line includes an FB-specific performance fix).

2026-01-22

—

2.3.3

Feature enhancement — Issue panel

Issue panel extended to display IVCUSTOM and IVSTATUS attributes. Platform: Jira Data Center 10.3.0 – 10.7.4.

2026-01-16

—

2.3.2

Feature enhancement — user mapping

Pagination and Delete all for user data mapping. Platform: Jira Data Center 10.3.0 – 10.7.4.

2025-10-30

2.6.4 — SM line; FB line

—

SAP 2.6.4 — attachments, texts, partners

Builds on 2.6.3. Attachment encoding and encode/decode of content data. SWITCH_CUST improvements and fixes. Texts: sorting; plain-text content handling; removal of an unsupported heading option; multiple text IDs under one logical key. Partners: support for business partner GUID on partner fields. Placeholders in text mapping: newline / line-feed / CR+LF patterns.

2025-10-23

—

2.3.1

Bugfix — input sanitization

Fixed overly aggressive input sanitization. Platform: Jira Data Center 10.3.0 – 10.7.4.

2025-10-15

—

2.3.0

New feature — DB Entry Editor

Under Queue Processing on the admin screen: ad-hoc overwrite of field values on synchronization queue entries. Platform: Jira Data Center 10.3.0 – 10.7.4.

2025-10-14

2.6.3 — SM line; FB line

—

SAP 2.6.3 — CONV, value mapping, value help

Builds on 2.6.2. Conversion improvements using context objects; more flexible value mapping and fixes for single-value arrays; JSON array handling; clearer log option parameter texts. More customer-friendly value help.

2025-10-07

2.6.2 — SM line; FB line

—

SAP 2.6.2 — customizing delivery, mapping

Builds on 2.6.1. Translation for inactive flags; customizing tables delivered with delivery type A; array mapping fixes.

2025-10-02

2.6.1 — SM line; FB line

—

SAP 2.6.1 — mass sync, JSON, attachments, OData

Builds on 2.6.0. JSON optimizations and automated tests; test data container support. Sync log: delete options; mass sync and PPF mass sync improvements; missing final sync messages addressed; more control over mass-sync logging and consistent SLG1 logging of sync status (including PPF). Attachments: file extension handling; BADI implementation and customizing adjustments. Partners: safer user conversion routines; multiple partners. OData service scoped to PUT/POST entity sets for CPI / API management style integration. Correct ticket id and URL after create; duplicate scope fixes (including FB-specific case); Jira Data Center configuration fix; ticket id sorting in reports; stability when transactions are already closed; exception logging optimization; issue link customizing; truncate long text on outbound send. Issue link documentation updates.

2025-07-18

2.6.0 — SM line

—

SAP 2.6.0 (SM) — issue links, JSON arrays, attachments

CC4 customizing. Issue links and broader architecture updates. Support for very large select options. Attachment filename pattern checks. Fewer duplicate comments when syncing from Jira to Solution Manager. Evolution of JSON / array handling. New customizing delivery transport. (Focused Build 2.6.0 delivery is the companion row dated 2025-07-17.)

2025-07-17

2.5.3 — SM line

—

SAP 2.5.3 (SM) — delta on 2.5.1 line

Small delta on the 2.5.1 SM stack per export; confirm naming with your SAP cut list if the delivery title and contained list disagree.

2025-07-17

2.6.0 — FB line

—

SAP 2.6.0 (FB) — scopes, SPAU, FB phase

Stack includes the prior 2.5.2 FB delivery baseline plus Focused Build create/update scope, requested phase for work items, SPAU enhancement, and the same broad themes as the SM 2.6.0 line (customizing, issue links, attachments, JSON arrays, duplicate comments, customizing delivery transport).

2025-06-04

2.5.1 — SM line

—

SAP 2.5.1 (SM) — queuing, ChaRM, scopes

Builds on 2.5.0 SM. Exception handling uses PREVIOUS as a parameter; CSRF token handling adjusted. Enqueue after save and TEXTLOG detection for transaction creation. Configuration Item assignment. ChaRM conversion updates. OData queuing/sequencing for calls. Scope create/update (standard line). Queuing for internal/update calls with per-user wait behaviour.

2025-06-04

2.5.2 — FB line

—

SAP 2.5.2 (FB) — scopes, queuing, ChaRM, cycle

Builds on 2.5.1 FB baseline. Same themes as 2.5.1 SM (exception handling, CSRF, enqueue/TEXTLOG, configuration item, ChaRM conversion, OData queuing, scope create/update, internal queuing) plus Focused Build scope create/update and cycle handling for FB.

2025-02-11

2.5.0 — SM line

—

SAP 2.5.0 (SM) — logging, attachments, usermap, HTTP

Builds on 2.4.0 SM. Generic customizing. Unassign user via null; mass sync report fixes; user mapping report (Jira) fixes; transaction log; PPF add-on; leading zeros; inbound support for sold PO number field; report layout defaults. Logging improvements and correction flows (including legacy review path). Jira Cloud attachment redirect support; priority checks; HTTP client without popup on 401; attachment timezone handling; text log document class supports additional BUS20002* transactions; transaction read and URL optimization; sold PO number on change-request action.

2025-02-11

2.5.0 — FB line

—

SAP 2.5.0 (FB) — generic customizing

Export shows generic customizing only for this FB version line; further FB functional content lands in the subsequent 2.5.1 FB delivery.

2025-02-11

2.5.1 — FB line

—

SAP 2.5.1 (FB) — same as 2.5.0 SM stack + FB activation

Builds on 2.5.0 FB; contained scope aligns with the large 2.5.0 SM feature set (logging, attachments, user mapping, HTTP, PPF, etc.) plus activation of FB transaction enhancements and repeated correction transports for the same themes.

2024-08-15

2.4.0 — SM line

—

SAP 2.4.0 (SM) — baselines, CF packages, REST

Baseline improvements from early 2024. Cross Framework (CF) component baselines (exceptions, PPF, conversion, transaction log, JSON, REST, BADI). User mapping updates; SICF service; email ↔ external user mapping; namespace packages for Cross ALM / CRM / SM stacks. Delivery baseline without Focused Build; customizing ready for delivery; optional sync actions; SERVICE_OS fix; REST improvements; default status reason; final customizing delivery.

2024-08-15

2.4.0 — FB line

—

SAP 2.4.0 (FB) — baselines + FB package

Same CF / package / user mapping / SICF themes as SM plus Focused Build delivery baseline from March 2024, FB enhancement adjustment, and customizing delivery.

Release 1 2025

2.5.0

2.0.1

May 6, 2025

Minor enhancement Jira side

Enhanced attachment handling on Jira 10 side.

2.5.0

2.0.0

Mar 24, 2025

Jira 10 compatibility

CC4 is now compatible with Jira 10.

2.5.0

1.8.0

Apr 7, 2025

Minor enhancement Jira side

Enhanced attachment handling on Jira side.

2.5.0

1.7.0

Feb 11, 2025

Improvements & bug fixes

Improvements:

• When a status change is triggered from Solution Manager side, the respective Jira transition is now determined by transition name + ID instead of just the transition name.

• It is now possible to send field update calls from a transition screen in Jira. Before, only a status update call was sent to SAP Solution Manager.

Bug fix (SAP):

• CC4 log error: Not every sync action was logged in the CC4 log when two PPF actions were performed sequentially.

• CC4 log error: If a final status was set through a sync action, the action was not logged in the CC4 log.

• Tool bar button with jump-in link to external ticket: If parameter IM_READONLY_AFTER_SAVE was set to “X” in table AGS_WORK_CUSTOM (SolMan switches to “Display” mode after saving a transaction), the coding for the tool bar created a lock for the transaction. Jump Link Button in CRM Web UI

• Sending and handling of attachment date/time information was changed to UTC.

• Mass sync report: performance enhancements + translation issues fixed. Triggering Mass Synchronization

Bug fix (Jira):

• Issues with “Re-Sync” button.

• Sending and handling of attachment date/time information was changed to UTC:
  If the server on which the Jira instance runs is located in a different time zone than the server, where the SAP Solution Manager runs, the synchronization of attachments might not work. When sending attachments from SAP Solution Manager to Jira, the timestamp of when the attachment was last changed is compared to the last synchronization date between the Jira and the SAP transaction. If the attachment timestamp is older than the last synchronization timestamp, the attachment is not added to the Jira transaction. A change was implemented where now both timestamps are compared in UTC.

Release 2 2024

2.4.0

1.5.4

Dec 2, 2024

Minor enhancement Jira side

Some more log entries were added on Jira side regarding the attachment synchronization.

2.4.0

1.5.3

Oct 31, 2024

Improved update performance

Improved handling of dependencies during CC4 app update.

2.4.0

1.5.2

Oct 31, 2024

Minor enhancement Jira side

If an unmapped user is entered in a partner field that should be synchronized (e.g. “Assignee”) an error message is displayed in Jira. Additionally, a detailed error information which user is unmapped can be found in the Cross Connector log.

2.4.0

1.5.1

Sep 30, 2024

Minor enhancement Jira side

Improved error logging on Jira side

2.4.0

1.5.0

Aug 19, 2024

Improvements & bug fixes

Improvements (SAP):

• A mass sync report is now available on Solman side. Triggering Mass Synchronization

• A helper report is now available determining the Jira User ID for all SAP users to be used for ticket synchronization. This Report can be used to build/update the user value mapping configuration of CC4. https://crossalm2.atlassian.net/wiki/x/AoC7nAE

• A new field “Filter” is now available in our field mapping configuration.

• New, unified way to send a jump-in URL from SolMan to Jira.

• A Jump-In button can be configured in the overview page of SAP CRM Web UI jumping to the external ticket in the external tool. https://crossalm2.atlassian.net/wiki/x/DgAymQE

• External tool is now allowed to send attachment binary data directly instead of an URL. (not used by Jira side so far).

• All ITPPM fields are now supported.

Bug fix (SAP):

• Issues synchronizing long texts. (Wrong texts got sent to Jira)

• Issue with wrong business partner conversion.

• Issue with multiple business partners having the same e-mail address got fixed.

• Error in action SAVE_PARTNER. Please implement SAP note 3449736.

• Issues with dependent constant attributes got fixed.

• Attachment filename can now contain spaces.

• Issues with attachment synchronization got fixed. Error handling got improved. Binary data are now read directly instead of using a content server http get call. Wrong configuration got fixed (legacy configuration is still working).

• Customizing table /XALM/CC4_SFM_T1 got adjusted. Please check https://crossalm2.atlassian.net/wiki/x/DoBdnAE

Bug fix (Jira):

• Handling of Sprint field got adjusted.

• Empty comment was added after each synchronization.

We changed our Release Notes Design.