...
Make a copy of current migration (e.g. with Server ID SERVER_COPY)
Create a new entry from the template for Jira Cloud (e.g. with Server ID CUST_CLOUD_TEMPLATE)
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
Set deaktivate flag for the new entry (CUST_CLOUD_TEMPLATE)
TM Workflow step configuration
...
Make a copy for all item types of current migration (using same Server ID e.g. SERVER_COPY)
Copy all entries to the newly created Jira Cloud Server ID (e.g. Server ID CUST_CLOUD_TEMPLATE
Adapt filter query for the GET item
...
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}"
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
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
| Note |
|---|
The created ITSM ID for Jira Cloud settings must be created with the same name as used for Jira Server. |
TM Workflow step configuration
Inactivate entry for item type GET, that was used for server
Activate entry for item type GET, that was prepared for cloud