Versions Compared

Version Old Version 2 New Version 3
Changes made by

Bernhard Doleschel

Bernhard Doleschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Requirements in R4J are, at bottom, Jira issues, so when you migrate your Jira Data Center instance to a Jira Cloud instance, you have thereby also migrated your requirements - albeit without the extra data created by R4J.

There are three ways of migrating extra R4J data from R4J Data Center to R4J Cloud. All of them are only partial solutions, since they provide for the transfer of R4J project tree data but not for other data such as coverage views. However, even if a migration method is not available, certain sorts of R4J data can be recreated by hand.

The following sections explain which data can be migrated and the different migration methods, as well as which data can be recreated by hand.

Table of Contents
minLevel1
maxLevel7

What R4J data can be migrated or recreated by hand?

Data

Can be migrated?

Can be recreated by hand?

Comment

Project Tree

 (tick)

(tick)

Project tree data, including folders (folder name, description and attachments), can be completely migrated using one of the methods described below.

References to Confluence pages in project trees cannot be migrated.

Coverage

(error)

(tick)

Coverage views cannot be migrated but can be recreated by hand. This is due to a difference in query functions between Jira Data Center and Cloud.

Traceability

(error)

(tick)

Traceability is not yet supported in R4J Cloud, views cannot be migrated but can be recreated by hand when this feature is available. This is due to a difference in query functions between Jira Data Center and Cloud.

Baselines

(error)

(error)

Baselines cannot be migrated or recreated.

Administration configuration

(error)

(tick)

Configuration can be recreated by hand, but note that R4J Cloud administration is organized somewhat differently than DC administration.

Export templates

(error)

(tick)

Export templates should be downloaded by hand and then uploaded to R4J Cloud.

Info

Not all features of the template language are as yet supported in R4J Cloud, so export templates should be reviewed and possibly modified to work as expected. See the items labeled

Status
colourGreen
titleData Center only
in Context Item Types, Expressions and Statements.

Migration Methods

Self-service using ReqIF Files

With this method, you export the desired projects in the JIra DC instance to exchange files and then import these files into the Jira Cloud instance. The files are formatted in the Requirements Interchange Format Specification (REQIF).

  • In the DC instance, you first export project trees. The ReqIF files generated here will be used to import the structures to R4J Cloud.

  • In your Cloud instance, you then import the exported trees.

For a full description of the migration process, see How to migrate R4J from Jira Data Center to Jira Cloud using ReqIF.

Self-service using Python scripts and REST APIs

This method is suited for advanced users with programming knowledge. We provide an open-source Python script that illustrates the use of APIs to migrate R4J trees - see https://github.com/easesolutions/r4j-cloud-api-samples. The readme file provides all the needed information to run the script.

Note

Please note we cannot provide any support or warranties for the use of this method.

Professional Services

To minimize effort and reduce risks, you can have us perform the entire migration. Please contact the R4J support team for more information.