CC5 is able to assign a transport request to a tasklist of SAP Solution Manager. This article is describing the prerequisites, features and limitations.

A Tasklist has to be created and activated. The corresponding CTS project has to be configured in CC5 Jira app to be used for TR creation and TR assignment/coupling.

In the past there was a business function existing which needed to be activated. This business function is not existing/needed anymore.

https://crossalm2.atlassian.net/wiki/spaces/JXFB/pages/6345326597

https://crossalm2.atlassian.net/wiki/spaces/JXFB/pages/7379845144

1. You are creating a transport request using CC5 Jira App. Here you are assigning a CTS project which is assigned to a tasklist. Then the transport request will be assigned to the tasklist on creation.

2. You are assigning/coupling a transport request using CC5 Jira App. Here you are assigning a CTS project which is assigned to a tasklist. Then the transport request will be assigned to the tasklist on assignment.

3. There is a transport request existing in your managed system being controlled by CC5. It got created by CC5 or assigned/coupled to CC5. The CTS project was not set so far. Now you set a CTS project ID which is assigned to a tasklist. You are performing this change directly in your managed system using transaction SE01/SE09/SE10 . Then the transport request will be assigned to the tasklist on next read/refresh of CC5 in the corresponding Jira Ticket or in the CC5 Release Management Cockpit.

4. You are deleting a transport request using CC5 Jira App. The transport request was assigned to a tasklist. The assignment will be deleted.

5. You are deleting a transport request in managed system. The transport request was assigned to a tasklist. The assignment will be deleted on next read/refresh where the deletion will be detected.

1. Change of CTS project after creation via CC5 is not supported yet. Even decouple and re-couple of a transport request using another CTS project ID will not help. The original CTS project ID and its tasklist assignment will be kept for consistency reasons.

2. Change of CTS project after creation by using transport organizer in managed system is allowed but will not change the tasklist assignment. This will cause inconsistencies which could cause issues when controlling tr operations by the tasklist.

3. You cannot set the CTS project ID after creation or assignment of a transport request. There is no action implemented so far. As workaround you have to decouple and re-couple the transport request from and to your Jira ticket.

4. CC5-Decoupling of a TR is not deleting the task list assignment. The TR is still existing and still assigned to the original CTS project ID and its tasklist.

5. A transport request can be assigned to multiple Jira ticket at the same time since CC5 version 2025/05. However there still can be only one cts project and one tasklist assignment.

6. Tasklist assignment after creation is sometimes changing the TR description to a unwanted value “<tasklist id>: <landscape name>”. If you are facing this issue, please deactivate BADI implementation /TMWFLOW/UPD_DESC_ASSIGN_TR (BADI definition /TMWFLOW/ASSIGN_TRANS_DESC_UPD).

If you want to assign multiple transport requests to a certain CTS project and tasklist, you can use report /XALM/CC5_SM_ASSIGN_TR_TO_TL. Please note that this report is processing transport requests which are already known to CC5 and which are already assigned to a Jira Ticket. The limitations mentioned above are still valid here. Which means, that this report can be used for initial tasklist assignment but not for a tasklist re-assignment.

Please check logs in SLG1 afterwards.

Please perform a refresh afterwards using report /XALM/CC5_HELP_REFRESH_TR.

To speed up the processing and to avoid issues opening and closing CTS project status switches, you should open the project status switch for transport creation before running the report. Otherwise the status switch will be opened and closed for eah individual transport request.