CLOUD | DATA CENTER AND SERVER

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Overview

R4J Cloud supports requirements reuse via the copy and paste operation. Requirements in a project tree, including their folder structure, can be copied to a different folder of that project or to a folder in a different project. (This works also for any kind of issue type, not only for requirements.)

  • Copy folders only: If you have a good folder structure in one project, or in part of a project, you can copy that structure to a different project or to a different part of the same project. To do so, filter the sourcing project for folder issue types only.

  • Import folders and include issues: If you have some requirements in one project that are valid as is in other projects, you can include them in the other projects. The Jira issues representing the structure are added to target but not copied. Changes in the source issues are immediately visible in the other projects.

  • Copy folders and issues: If you have some requirements in one project that are valid in other projects, or in a different folder of the same project, but may require subsequent changes independently of the original requirements, you can copy them to the other projects or within the project. The requirements are then separate from each other and changes in the original requirements are not reflected in the copied requirements.

Reuse issues dialog

When copied items are pasted, the Reuse Issues dialog appears, in which a choice between the different forms of requirements reuse is made and additional options are selected.

After setting the options and selecting Paste, the Reuse Status appears. After the operation is finished the results are displayed. Error messages are shown in case of failures resulting from incompatible project configurations (e.g. a field for source project doesn’t exist in the target project).

The paste operation is executed in the background, so you can work on other R4J elements in parallel. Only one reuse operation can be launched at the same time.

Reuse Scenarios

Use Case

Description

Copy selected content

Select a folder or requirement in the project tree and select Copy in the context menu.

Create folders only

Before you start the paste, filter your tree structure by the folder issue type (in most cases “Folder”).

Paste content to target

Select the target folder in the same project tree, or in the tree of a different project, and select Paste in the context menu.

Create new issues

Select Create new issues to copy the issues as new issues in the target project.

Import structure as is

Select Import to tree to add all issues from source into the target project. Changes in the issues are immediately visible in all trees where the issues imported.

This option is only enabled if the target is in a different project.

Create links to new issues

Select a link type to create links in the source issues pointing to the copied issues.

Copy attachments

Use the toggle to enable or disable the copy attachments.

Copy child issues, sub-tasks and issues in epics

The contents include the requirements (as well as any child requirements), and any subfolders and their requirements, as deep as the folder hierarchy extends.
While Sub-tasks, Issues under Epic and Linked issues are only copied when they are in the tree listed as children of the source.

Field selection for the copy

All fields included in the source issues are copied to the target issue type as long it is write-able in the target project.

Link relation between copied issues

Links from parent issue to children automatically created. All other relations are not copied yet.

Copy entire project tree into a new project

  1. Create the new project in Jira, activate it for R4J.

  2. Select and copy the requirements and folders under the root folder of the first project

  3. Paste them to the root folder of the new project.

This practice could be useful if, for example, you have a template requirements project and want to ensure that new projects start from that template.

  • No labels