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

4. Set deaktivate flag for the new entry (CUST_CLOUD_TEMPLATE)

TM Workflow step configuration

...

1. Make a copy for all item types of current migration (using same Server ID e.g. SERVER_COPY)

2. Copy all entries to the newly created Jira Cloud Server ID (e.g. Server ID CUST_CLOUD_TEMPLATE

3. Adapt filter query for the GET item

...

1. from Server filter to Cloud filter

...

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

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

   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.

...