Migrating from Jira Server/Data Center to Cloud
Jira Server/Data Center applications are built on a different framework than Cloud applications.
What this means for R4J Cloud:
There is a gap in application maturity because Cloud development is young and still ongoing. Features in R4J Server/Data Center version may or may not be implemented in the Cloud version depending on customer feedback. We'll try our best to rollout the most important features you need first.
There are differences in data structure, infrastructure, and interface design. In R4J Cloud, we are given a clean slate to make different decisions to help with stability and usability which will improve you user experience in the long run.
Migration Path
We are currently developing a custom migration path between R4J Server/Data Center to Cloud. This will be done through the Requirements Interchange Format (ReqIF).
Further updates will be announced.
What R4J data can be migrated?
Tree Structure |
| The following data can be migrated:
Pages in tree cannot be migrated. |
Other features not listed | Coverage, traceability, and administration configurations cannot be migrated but can be transferred manually. Baselines cannot be migrated. |
Are the features different between R4J Server, Datacenter, and Cloud?
R4J Server and Datacenter share exactly the same features. However, the design or behavior of a feature in R4J Cloud may be different compared to the same feature in R4J Server.
Differences between Server/DC and Cloud version of R4J
Administration | |||
Feature | Server/DC | Cloud | Differences |
Permissions | Global and project permissions are not yet implemented in Cloud. | ||
Configuration | (as of v4.6)
| Though configuration is supported for both, the options are different. | |
Activate Projects | R4J Cloud can activate multiple selected projects at once and does not have the activate-by-project-category feature as R4J Server/DC does. | ||
API Tokens | Required for REST API authentication. | ||
Components | |||
Feature | Server/DC | Cloud | Differences |
Navigating to the R4J project | R4J Server/DC: Requirements Menu > Select a project R4J Cloud:
| ||
Tree View | Advanced features like reuse, auto-import, export, settings are not yet implemented in R4J Cloud. | ||
Detail View |
|
| Issue comparison are not yet implemented in R4J Cloud. |
Reading View |
|
| Display fields are not yet implemented in R4J Cloud. |
Coverage View | Saved coverage views in R4J Cloud are displayed in a tree structure and can be organized better. However, Display Fields and Export are not yet supported. | ||
Other features not listed | Cloud development is still ongoing. | ||