The ITSM systems are configured and activated in the configurations cockpit. The configuration cockpit of TM Integration Framework is called via the transaction /RTC/TM_IF_CONFIG. The section “ITSM System configuration” contains the configuration for the communication from SAP to Jira.
The assignment between transport requests and Jira issues are done by SAP attributes and, after the transport request has been moved to the Transport Manager, by the TM attributes.
The following two informations are stored in the SAP/TM attributes:
ITSM name (configured in the configuration cockpit)
Jira Issue ID
To be able to continue the communication from SAP to Jira and to be able to execute defined actions, it is important to ensure that the Jira issue ID's do not change after the migration and that the ITSM configuration has been adapted from the server to the cloud in the configuration cockpit.
Preparation BEFORE migration
ITSM System configuration
Make a copy of current migration
Create a new entry from the template for Jira Cloud
Adapt configuration
Server Path
RFC Destination
Automation Path
Automation RFC
Work items - If customer attributes is used to save Jira issue ID, then the attribute name must be changed
Automation - Add automation items
Development system - Add development systems
Optional settings - check optional settings
TM Workflow step configuration
The filter query for the GET item type must be changed from Server filter to Cloud filter.
Filters to take into account the development systems defined in the Jira project
Jira Server: project in projectsForProperty( devSystems, "~", {SYSID}_{MANDT} )
Jira Cloud: project.property[devSystems].content ~ "{SYSID}_{MANDT}"
Steps AFTER migration
Note used ITSM ID for Jira Server
Delete ITSM ID entry for Jira Server (a copy was made as preparation)
Copy in the preparation created Jira Cloud entry and save it with previously noted ITSM ID
The created ITSM ID for Jira Cloud settings must be created with the same name as used for Jira Server.