Migration Path
There are three ways to migrate an R4J Tree from Server or Data Center to the Cloud:
Self-service using REQIF files: In this method, you need to manually export the desired projects to intermediary Requirements Interchange Format Specification (REQIF) files and then import them into the Cloud.
In your Server/Datacenter instance, update R4J to version 4.10 or above. Export project trees via ReqIF Operations. The ReqIF files generated here will be used to import the structure to R4J Cloud.
In your Cloud instance, perform ReqIF import. Refer to ReqIF Migration Import.
Self-service using Python scripts and the REST APIs: This method is suitable for advanced users with programming knowledge. We provide an open-source Python script that exemplifies the use of the APIs to migrate an R4J Tree. You can find it here: https://github.com/easesolutions/r4j-cloud-api-samples. All the needed information to run the script and perform the migration is available in the readme file. Please note that when opting for this method, we won't provide you any support or warranties.
Professional Services: If you want to minimize your internal efforts and outsource the risks, you can hire us to perform the R4J trees migration. Please enter in contact with us for more information.
What R4J data can be migrated?
Feature
Migration support
Notes
Tree Structure
The following data can be migrated:
Activated projects
Folders (including folder name, description, and attachments)
Issues in tree
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.
Export templates
Can not be migrated. Please download them from Server/DataCenter for later use when export feature is available in Cloud.
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:
Projects Menu > Select a project > Requirements Management for Jira
Apps Menu > Requirements Management for Jira
Tree View
In R4J Datacenter, folders are internal entities while in R4J Cloud, folders are now Jira issues.
Advanced features like auto-import, export, settings are not yet implemented in R4J Cloud.
Detail View
Issue comparison are not yet implemented in R4J Cloud.
Reading View
Coverage View
Saved coverage views in R4J Cloud are displayed in a tree structure and can be organized better.
Other features not listed
Migrate issue data
The first step is to migrate the basic Jira issue data from your Data Center instance to your Cloud instance. Atlassian currently provides two tools to support the migration. See the Atlassian page Cloud migration methods for Jira to understand the differences and select the right tool for you.
| Tip |
|---|
Depending on the size and complexity of the Jira DC instance, migration can be a daunting task. We recommend involving Atlassian support in your migration effort. A good place to start is the Atlassian page Choose a Cloud migration method. |
Export R4J tree data
The next step is to export R4J data from your Data Center instance in the “ReqIF” format. The procedure depends on the version of R4J you are using:
R4J 4.10 or later: You should use the bulk ReqIF export - see ReqIF Operations. Be sure to include all the R4J projects you want to appear in Jira Cloud.
Previous R4J versions: You must individually export each project using a required mapping configuration. See the following pages that explain how to configure this mapping and generate a project-specific export:
| Expand | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
R4J Issue Specification Type = Issue R4J Folder Specification Type = folderSpecType
|
Prepare Jira Cloud
Set the folder Issue type - see Specify Folder Issue Type.
If you use security levels:
Add the project role “atlassian-addons-project-access“ to “Browse Project“ permission in all the security levels configured for the projects to be migrated - see Manage project permissions.
Temporarily set the default security level to “None” in all issue security schemes used by the projects to be migrated - see Configure issue security schemes. This is necessary so that folder issues can be created during import. After the import, you will set the default security level back to the original level.
Import R4J tree data
The final step is to import the R4J data in the “ReqIF” format that you exported in the previous step.
Go to Settings > Manage apps > ReqIF Import in the R4J section.
Upload the exported ReqIF files.
Select Validate. After validation, you will be notified about how many issues will be created or moved and about any errors. Validation allows you to identify problems and solve them before the actual import of data.
Select Start new import. The process runs in the background. Refreshing the page shows the current status of the import.
If you use security levels, after the import finishes you should do the following:
Change the security level from “None” back to the original level.
Search for folder type issues and set their security to the desired level with a bulk edit.
Limitations
If a folder was created via the reuse functionality of R4J DC:
In versions below 4.11, its attachments will not be migrated.
In versions 4.11 and above, its attachments will be migrated IF it was reused with copied attachments.