Migration Guide: Moving from SAP Transport Integration for Jira Server to SAP Transport Integration for Jira Cloud
Feature comparison
Category | Feature | Server / Data Center | Cloud | Comment |
|---|---|---|---|---|
Issue view | Smart Change right web panel | ✔️ | ✔️ |
|
The Smart Change table logs | ✔️ | ✔️ |
| |
SAP TM TR Create | ✔️ | ✔️ |
| |
SAP TM TR approve | ✔️ | ✔️ |
| |
SAP TM Logon | ✔️ | ✔️ |
| |
SAP TM Logoff | ✔️ | ✔️ |
| |
Project settings | The TM Project settings | ✔️ | ✔️ |
|
SAP TM Issue Filter | ✔️ | ✔️ |
| |
Synchronize issue properties | ✔️ | ✔️ |
| |
Synchronize AO data | ✔️ |
| Not needed as data is saved only on Jira REST APIs | |
The TM Project features | ✔️ | ✔️ |
| |
App configuration page | The TM Controller configuration | ✔️ | ✔️ |
|
Workflow validators | SAP transports imported | ✔️ | ✔️ |
|
Workflow post functions | SAP TM TR approve | ✔️ | ✔️ |
|
Searchable issue properties | Searchable properties | ✔️ | ✔️ |
|
JQL functions (cloud does not provides JQL functions enhancements) | Issues in parent | ✔️ |
| Not needed by the apps |
Projects For Property | ✔️ |
| For cloud, projects properties can be used instead (For Jira server, the project properties are not searchable) Server: project in projectsForProperty( devSystems, "~", {SYSID}_{MANDT} ) Cloud: project.property[devSystems].content ~ "{SYSID}_{MANDT}" | |
SAP transports imported for level | ✔️ |
| For cloud, jira expressions can be used instead https://developer.atlassian.com/cloud/jira/platform/jira-expressions/ |
Prerequisites
The AO tables must be updated (Project setting → Synchronization) and finished before starting the migration.
Migration
The server and cloud apps supports the migration of the data stored in the AO tables (SAP transports data).
The data stored in the entity properties such as the App configuration (TM controller https://rtcom.atlassian.net/wiki/spaces/CONNECT/pages/433979609/Jira+App#Manage-TM-Controller ) and project settings (https://rtcom.atlassian.net/wiki/spaces/CONNECT/pages/433979609/Jira+App#Project-settings ) must be manually added after the migration has finished.
Please take in consideration of updating issue properties (Project setting → Synchronization) if they are used.
For a good performance of the data migration these settings must be done after the app migration completed 100% and it is recommended to wait ~15 minutes to make sure all cloud requests that might be in queue are completed on Jira cloud side as well.
To check that all SAP transports have been migrated the ‘tmTransports’ issue property can be used.
e.g.: Jira Server JQL issues: issue.property[tmTransports].content ~ ‘a*' and project = '<migratedProject>’
Jira Cloud JQL issues: issue.property[tmTransports].content ~ ‘a*' and project = '<migratedProject>’
The server issues must be equal with the returned cloud issues.
In case of app migration fails, the Migration Assistant provides the possibility to re-run the migration .
Atlassian’s Cloud Migration Assistant tool notes:
App migration status update in Cloud Migration Assistant user interface ( )
The Jira/Confluence Cloud Migration Assistant user interface does not display status updates from your cloud app in real-time.
There can be an interval of up to 10 minutes between the time your cloud app provides a status update and when the message is displayed on the Jira/Confluence Cloud Migration Assistant user interface.