Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Current »

CC5 DC Version

SAP (ABAP) version

Jira app version

Date

Release summary

Release Notes

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 featre: SLG1 Logging for transport request actions.

  • Bug on calculation of status “Ready for production” got fixed for single and two tier landscapes. Status will stay “Waiting for Import” and “Released” or 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:

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

Small Bugfix

Bugfix with deleted TRs for the issue property feature

2.3.9

Security Improvement

Removed a vulnerability

2.3.8

Small Bugfix

Bugfix with ToCs for the issue property feature

2.4.4

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

Bug fixing and Improvements

  • Upload Feature improvement: Drag and Drop available

  • Bugfix for RM Cockpit for old ToCs

2.3.6

Bug fixing

  • Adjust file size limit for upload feature

2.3.5

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

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

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

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

“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

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

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

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

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

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

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

Solman independent option
S/4HANA support
Better landscape support
Some improvements & fixes & tools

Deployment options: Solution can run either in SAP Solution Manager accessing managed systems via TMW RFC destinations (original use case) or directly in managed ABAP system where no SAP Solution Manager is needed (new use case).

CTS Support: S/4HANA Private Cloud and S/4HANA On Premise are officially supported. Maybe they were already supported in the past, but now it got validated. S/4HANA Public Cloud and cTMS are currently not supported. CTS+ and gCTS might be supported but not validated so far.

Landscapes: Support for landscapes with client independent transport routes (CTC=0). Support of cross transports (transports with a target not being a consolidation route). Fix for landscapes with parallel transport routes to determine best/shortest route correctly.

Simplification: Business function activating task list integration got removed. This feature is now always switched on by using a cts project id being connected to a task list.

Authorities: No additional authorities are needed in order to perform imports to the system & client where CC5 is running. Prior to this version, the technical CC5 user needed additional import authorities because RFC destination NONE was used.

Performance: Again some improvement of performance on reading transport request data, transport routes and import status. The read/refresh is now getting performed asynchronously, prior to this version it was performed synchronously. New transport status “Import running” got introduced.

Support: Some new helper reports are now available which can be used for analysing and solving issues:

  • /XALM/CC5_HELP_GET_LANDSCAPE

  • /XALM/CC5_HELP_REACTIVATE_TR

  • /XALM/CC5_HELP_DELETE_TR

  • /XALM/CC5_HELP_DELETE_TR_MULTI

  • /XALM/CC5_HELP_REFRESH_TR

  • /XALM/CC5_SM_TL_REFRESH_TR

2.1.11

2.1.6

2.1.11

Better Jira 9 Support

Changes to the way Jira loads JavaScript in the background required some adjustments

Additional improvements on Jira side:

  • Timeout issues fixed if action is taking longer than one minute.

  • Coupling of more than 5 transport requests at the same time is now possible.

  • Optionally jump-in to Transport Organizer Web UI instead of Classical Transport Organizer (SE09).

2.1.10

2.1.6

2.1.10

Hotfix

Added a Null Pointer Check before entries are read from DB as this caused issues in rare occasions

2.1.9

2.1.6

2.1.9

Hotfix

2.1.8

2.1.6

2.1.8

Import Subset and Info Popup

When multiple Transports are imported this is now done in the same action instead of separate calls.

Transport Information is now displayed in a separate Popup

2.1.7

2.1.6

2.1.7

Performance Improvements, Bug fixing and Mass Couple

Performance improvements on Jira side, editing ticket while loading CC5 data is now possible.

New feature: Mass couple of multiple transport requests.

Bug fixing for mail template and license warning.

2.1.6

2.1.6

2.1.6

20.03.2023

Performance Improvements

Eliminate timeout issue on transport data refresh avoiding endless hour glas on refresh.

Improvement of performance on reading transport request data, transport routes and import status.

Fix of import status calculation for landscapes without domain link (status was calculated wrong in some circumstances).

Open and close CTS project status switches on import, if needed.

2.1.5

06.02.2023

Bug fixing

  • Bug fixes:

    • Import feature is only working with domain-links → Solution is now working with and without domain-links.

    • Transport route determination is causing error messages in TMS Alert viewer if working without domain-links. → Solution is now working with and without domain-links.

    • Transport status & details & next import systems are sometimes calculated wrong. → Solution got completely reviewed, re-implemented, fixed and improved. It is now more stable, supporting more landscapes and is calculating better results.

    • Transport status tooltip is sometimes cutted and has sometimes no line breaks.

    • Some error messages are not helpful. Seems that especially error messages from TMS are incomplete (i.e. importing a TR with component version mismatch) → fixed. Error messages from TMS are now populated correctly.

  • Improvements:

    • A configuration can now have a description.

    • Customer action labels are now getting synchronized/updated during refreshing after triggering a TR action manually in managed system.

    • Transport buffers are getting synchronized/transmitted if needed before import.

    • A nice error message is getting shown if system is currently not available or disabled.

2.1.0

12.2022 (Beta Release)

Small improvements & bug fixing

  • Defaulting of import options & button visuability

  • Optimization of transport route determination

  • Adjustment of YAML (Swagger.IO) file

  • Bug fixing import action & details & log

2.0.0

10.2022 (Beta Release)

Assign & Import action with a lot of “related” improvements.

  • Action to import transport requests

  • Action to assign/deassign transport requests

  • Dealing with external transport requests

  • ChaRM integration (assign transport requests to ChaRM task lists on release, disallow ChaRM bypassing)

  • UI optimizations and improvements (button icons, fields, tooltips, popup design, …)

  • Logic improvements (error handling, buffering, …)

  • Notification improvements (additional parameters for mail form)

Supported deployment/import options:

  • Import button

  • Deployment via ChaRM task list

  • Deployment via gCTS (e.g. Jenkins Pipeline)

1.0.7

30.05.2022

URL Change for actions & Spring vulnerability patch

  • New URLs for DELETE and RELEASE actions.

  • Customers who are using a firewall to accept connections from the Add On must likely change the configuration since the URLs changed (including swagger.io files)

  • Added Patch for Spring Vulnerability by updating it's dependency.

1.0.6

08.12.2021

Cross Connector for TMS provides new updates

1.0.5

03.05.2021

SAP Cross Connector Transport Management System now available for Data Center

1.0.4

New functionalities

  • Language support in German and English

  • Release of transport request

  • Authorization control

  • Connection parameter for proxy system

1.0.3

Small new functionalities

  • Assignment of multiple Development Systems

  • Add Tasks on creation of Transport Request

  • Enhancements on the Transport Request Grid

  • Auth. check in Admin Panel

  • Performance improvement

1.0.2

14.04.2021

Cross Connector for TMS provides new updates

  • Performance improvement

  • CTS Project can be informed for creating Transport Requests

  • Jump-in URL to access Transport Requests in SAP

  • Status based Read-Only configuration for Final Status

  • New Email Notification framework

1.0.1

22.03.2021

Cross Connector for TMS provides an easy way of control over ticket transport

  • No labels