Tasklist Integration
CC5 is able to assign a transport request to a tasklist of SAP Solution Manager. This article is describing the prerequisites, features and limitations.
Prerequisites
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.
Features / Actions
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.
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.
There is a transport request existing in your 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 which is assigned to a tasklist. 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.
You are deleting a transport request using CC5 Jira App. The transport request was assigned to a tasklist. The assignment will be deleted.
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.
Limitations
Change of CTS project after creation via CC5 is officially not supported yet. There is no option implemented so far changing the transport request except adding some tasks.
Inofficially you can decouple a TR and couple it using another cts project if configured in CC5 Jira App. However in this case the tasklist assignment is not getting changed.
Change of CTS project after creation by using transport organizer in managed system is not changing the tasklist assignment.
CC5-Decoupling of a TR is not deleting the task list assignment.
A transport request can be assigned to only one Jira ticket at the same time. Exception: Source system is different: You want to deploy one transport request thru multiple system tracks in this case. This is only possible if the transport request is already released which implies that the CTS project assignment cannot be changed anymore.
A transport request can be assigned to only one cts project and tasklist at the same time.
Tasklist assignment after creation is changing the TR description to a unwanted value (only true if CTS project is set after creation and if BADI implementation /TMWFLOW/ASSIGN_TRANS_DESC_UPD is active).