Page Comparison

...

1. Make a copy of current migration (e.g. with Server ID SERVER_COPY)

2. Create a new entry from the template for Jira Cloud (e.g. with Server ID CUST_CLOUD_TEMPLATE)

3. Adapt configuration in the new entry

   • 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

...

The filter query for the GET item type must be changed from Server filter to Cloud filter.

1. Create a new entry for the current ServerID with item type GET.

   1. Adapt filter entries

      • 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}"

   2. Set created entry as inactive

2. Optional action can be copied also from Jira Server entry to the newly created Jira Cloud template (CUST_CLOUD_TEMPLTE). That allows a test for the template configuration.

Steps AFTER migration

ITSM System configuration

1. Note used ITSM ID for Jira Server

2. Delete ITSM ID entry for Jira Server (a copy was made as preparation)

3. Copy in the preparation created Jira Cloud entry and save it with previously noted ITSM ID

TM Workflow step configuration

1. Inactivate entry for item type GET, that was used for server

2. Activate entry for item type GET, that was prepared for cloud