Jira 11

3.0.3

2.6.2

31.03.2026

Jira Data Center 11

Jira: Aligns with Jira Data Center as offered on the Marketplace (including version 11) and improves everyday use: more reliable connection to SAP Solution Manager, clearer administration and safer handling of integration settings, transport actions that respect issue status, faster loading of transport lists on issues, simpler import steps (including selecting several items at once and adding multiple transports in one upload), copying visibility settings between profiles, and better control over which actions different users see. General stability and error handling improvements.

SAP: Use SAP ABAP 3.0.3 with this app. The ABAP changes for 3.0.3 are described in the following row

Jira 10

3.0.3

2.5.0

19.03.2026

SAP ABAP delivery 3.0.3

SAP: Corrections for remote-system domain determination and related assignment behaviour. Improvements for assignment of external transport requests and assignment details. Import the managed system and Solution Manager delivery packages for 3.0.3 supplied by Cross ALM, together with Jira 2.6.2 (or as directed by your administrator).

3.0.2

2.5.0

02.12.2025

SAP ABAP delivery 3.0.2

SAP: Multi-client import improvements, transport-of-copies target selection, clearer error forwarding (including SAP Business Technology Platform where relevant), logging-related stability, and Solution Manager RFC handling updates. Jira app 2.5.0 remains supported on this SAP line until you move to 2.6.2 and 3.0.3.

3.0.1

2.5.0

05.11.2025

SAP ABAP delivery 3.0.1

SAP: Fixes for abnormal terminations during Transport of Copies creation and related stability.

3.0.0

2.5.0

17.07.2025

SAP ABAP delivery 3.0.0

SAP: New 3.0.x product line after 2.6.0: foundation for transport-related checks, multi-couple handling, whitelist and logging extensions, asynchronous processing, improved handling of virtual systems in the landscape, and CTS-related fixes.

2.6.0

2.5.0

22.05.2025

Jira Data Center 10

Jira: Supports Jira Data Center 10 and updates the user interface for the current Atlassian platform.

SAP: Requires at least SAP ABAP 2.5.0; apply subsequent SAP deliveries (2.5.1, 2.5.2, 2.6.0, 3.0.x) as described in the rows above and below, per Cross ALM.

Before Jira 10 (Legacy)

2.6.0

2.4.5

10.02.2025

SAP ABAP delivery 2.6.0

SAP: Builds on 2.5.2: logging stability, transport-of-copies in Ready for production, create/couple with task-list assignment, whitelist checks, blocking transport-of-copies when empty, user mapping, and import/refresh corrections.

2.5.2

2.4.5

10.10.2024

SAP ABAP delivery 2.5.2

SAP: Builds on 2.5.1: checks for empty transport requests, user mapping and logging improvements, Ready for production handling for changeable transport requests, nested logging, business-object field adjustments, and related corrections.

2.5.1

2.4.4

15.08.2024

SAP ABAP delivery 2.5.1

SAP: Follow-up to 2.5.0: correction for CTS helper open-output behaviour.

2.5.0

2.4.4

15.08.2024

SAP ABAP delivery 2.5.0

SAP: First 2.5.0 product delivery: managed-system foundations, virtual systems, exception handling, add-task/user fixes, bugfixing collection for the 2.4.0–2.4.4 maintenance window, lock avoidance, parallel import behaviour, and correct status when import is scheduled.

—

2.4.5

17.10.2024

Small bugfix

Jira: Corrects refresh of uploaded transport requests when the same transport appears on more than one Jira issue. Further improvements to configuration and CTS project handling after 2.4.4.

SAP: No dedicated SAP version tied only to this Jira update; keep SAP CC5 on a supported release (from 2.5.0 upward).

—

2.4.4

07.10.2024

Bugfixing

Jira: Configuration page revised so SAP systems are listed reliably. Improvements for CTS projects and related configuration; clearer behaviour when opening settings dialogs.

SAP: Maintenance through 2.4.0–2.4.4 is included in the 2.5.0 SAP delivery (see row above).

2.6.0

not released yet

Small improvements

SAP:

• Additional check: Allow ToC creation only if TR has no open tasks and if TR is not empty.

• Additional feature: SLG1 Logging for transport request actions & checks.

• Bug on calculation of status “Ready for production” got fixed for single and two tier landscapes. Status will stay “Waiting for Import” and “Released” in these special cases.

2.4.5

17.10.2024

Small Bugfix

​Fix refresh from uploaded Transport Requests. If one TR is in multiple Jira Tickets the refresh did not work correctly

2.4.4

16..10.2024

Bugfixing

Jira:

• the configuration page was revised, as some SAP systems were sometimes not displayed correctly.

2.4.3

16.10.2024

Downward compatibility

Jira:

• we have adapted the downward compatibility of the Java version and now also support Java 1.8.

2.4.2

19.09.2024

Bugfixing

Jira: fix CTS Project support

2.4.1

17.09.2024

Bugfixing

Jira: configuration page was incomplete

2.5.2

17.09.2024

Bugfixing

SAP: Fixing refresh issue on transport requests assigned to a task list and deleted manually

Release 2 2024

2.5.1

2.4.0

12.09.2024

“Initial Version of Release 2 2024”

Jira:

• Status-dependent display TR Action Buttons (please check the documentation: Status-dependent Transport Action Display - Cross Connector - Confluence (atlassian.net))

• Complex search/query for Jira issues by TR properties (TR ID, TR Owner, TR Status, Next System, …)

• Simplified TR Upload Popup

• Some Release Management UI Improvements/Fixes

SAP:

• Calculation of TR status got refactored/improved. Maybe some wrong calculation of TR status or import details got fixed.

• Introducing new TR status “Import scheduled” and “Ready for Production”.

• Import details text is now informing about component version mismatch and need for “add to buffer” and “transmit buffer” activities.

• Import details text is now informing about systems where import has to be performed in a latet step.

• Some very special buffer issues got fixed.

• We are now supporting virtual systems as part of the TMS landscape.

• Refresh issues during ToC creation or TR Import got fixed. Enqueue mechanism is no longer blocking a read.

Release 1 2024

2.3.10

Aug 8, 2024

Small Bugfix

Bugfix with deleted TRs for the issue property feature

2.3.9

Aug 6, 2024

Security Improvement

Removed a vulnerability

2.3.8

Jul 25, 2024

Small Bugfix

Bugfix with ToCs for the issue property feature

2.4.4

Jul 18, 2024

Bug fixing

SAP:

• Fixing issues ignoring LMDB lifecycle status. It got sometimes not ignored and was causing error messages. This fix is only relevant if CC5 is installed on a SAP Solution Manager system and if CC5 should work even if a system is temporarily inactive.

2.3.7

Jul 18, 2024

Bug fixing and Improvements

• Upload Feature improvement: Drag and Drop available

• Bugfix for RM Cockpit for old ToCs

2.3.6

Jul 10, 2024

Bug fixing

• Adjust file size limit for upload feature

2.3.5

Jun 13, 2024

Improvements

• Early Beta Feature for consistency checks: Issue properties for transport request status available

• RM Cockpit is only visible in CC5 projects

2.4.3

2.3.3

Jul 3, 2024

Bug fixing and UI Improvements

Jira:

• Improved error handling and logging for the upload feature

• button wrap for different screen resolutions

SAP:

• Fix Issue releasing ToC of workbench transport requests

• Fix issue internally buffering system data. This issue was causing dumps in None-Solman scenario.

2.4.2

2.3.2

May 16, 2024

Bug fixing

Better error messages when upload is failing, in case transport request is already existing in transport directory.

Refresh of import queue buffer after buffer transmit is now avoiding errors on subsequent TR import.

Fix issue reading CTS Project from TR. This issue was causing a lot of issues and error messages if working with CTS projects. This issue was existing since version CC5 ABAP 2.4.0.

2.4.1

2.3.1

May 9, 2024

Bug fixing and small improvements

Bug fixing:

• Errors during upload are now displayed after execution. In previous version upload feature returned always a success even if it got failed.

Improvements:

• We are now checking whether cofile and datafile are having proper names. a cofile should start with K and a datafile should start with R.

• We are now checking whether transport to be uploaded is an external (and not an internal) transport request. We are analyzing the first three letters of the filename here.

2.4.0

2.3.0

Apr 19, 2024

“Initial Version of Release 1 2024”

Upload Feature, Multiple Backends, Bug fixing

Improvements:

• A new button can be configured to upload transport files of an external transport request to the transport directory of the development system.

• Jira side can now be connected to multiple ABAP backend systems (SAP Solution Manager or S/4 HANA or ECC or …) previously only one connection to a central backend system was possible.

• Some error messages (especially from tp) are now more precisely resp. end-user friendly.

• Some performance improvements got implemented.

Bug fixing:

• Ignoring LMDB lifecycle status

• Transmitting buffers (data & cofiles) across transport directories.

• Importing multiple transport requests in one shot

• Importing subset into multiple clients of the same system in one shot.

• Importing a list of transport requests in a sequence checking the RC of each transport request stoping import on RC > 4.

• Importing ToCs in all configured follow-up systems (not only one)

• Some buffer issues got fixed.

We changed our Release Notes Design.

2.3.1

2.3.0

2.2.1

Feb 12, 2024

Experimental Loading Change

We are implementing a change with this version that firstly changes some logic about how and when transports are loaded when an issue is loaded.

Now transports will NOT be loaded by themselves! You will have to refresh the data yourself. A timestamp now informs you when the information was last loaded.

We are aiming to provide a solution where you can configure the best moment to load your data based on your jira config.

2.3.0

2.3.0

2.2.0

Jan 29, 2024

Transport of Copies!

This version of our app introduces the possibility to create ToCs in your SAP Q-System directly from Jira!

Please note, that you will have to upgrade your SAP Version for this feature to work.

Buffer synchronization got improved now supporting landscapes with multiple transport directories. Related error messages on import will not occur any longer.

2.2.5

2.2.2

2.1.19

Nov 24, 2023

Customizable TR description and custom text for actions

The description for transport request is now no longer hard coded and can be defined by you in the manage apps section. This can also include values of custom fields.

When using custom actions you can now define text that you can embed into the mail that is being sent out.

2.2.4

2.2.2

2.1.18

Nov 23, 2023

Bugfixes and Customer Actions in RMC

Added the option to execute customer actions to the release management cockpit as well as links to issues

2.2.3

2.2.2

2.1.16

Nov 8, 2023

Bugfixes

Fixed bugs related to dependencies loading incorrectly. This fixes an issue with the labels drop down as well as transports only loading after an additional refresh

2.2.2

2.2.2

2.1.14

Oct 16, 2023

Release Management Cockpit + Sorting

Increase performance, add a release management cockpit and add the option for sorting transport order on ticket basis (used as import sequence if import single is requested).

Bugfixing of some abap helper reports.

2.2.1

2.2.1

2.1.11