Versions Compared

Old Version 5

changes.mady.by.user Bernhard Doleschel

Saved on

compared with

New Version Current

changes.mady.by.user Niel Flores

Saved on

Key

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

Overview

R4J easeRequirements 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.) The following reuse scenarios are supported:

  • 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 as is: If you have some requirements in a folder structure 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 projectsby reference. Users then have one copy of a folder or issue, but it is visible in different places, and any changes made in one place are immediately seen in all places.

  • Copy folders and issues: If you have some requirements or folders 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 requirementsissues, you can copy them to the other projects or within the same project. The new requirements and folders are then separate distinct from each other their sources and changes in the original requirements issues are not reflected in the copied requirementsthe copies.

  • Copy entire project tree into a new project: If you have a requirements project and want a new project to start from the current state of that project, you can copy its folders and requirements into a new project. For example, you have a template project that you want to use as the starting point for every new project.

Table of Contents

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. The following options are available:

Option

Description

Comment

Method

Choose between two different kinds of reuse:

  • Create new issues: This option results in each issue being copied into the target project.

  • Import to tree: This option results in references to the issues being created in the target project.

Only available if the destination is a different project. If the target is the same project, issues can only be copied.

Copy attachments

Enable or disable the option to copy attachments.

Only available when copying issues.

Create links to new issues

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

Only available when copying issues.

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 used in the source project doesn’t exist in the target project).

Note

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

refreshing the page does not cancel the operation. Currently, only one paste operation at a time is allowed per tree.

The paste operation for copied issues achieves the following results:

  • The requirements, as well as any child requirements, and any subfolders and their requirements, as deep as the folder hierarchy extends, are copied as new folders and issues. Note that only issues in the source tree structure are copied. Issues related to them - such as subtasks, issues in epics and linked issues - are not automatically copied. You can get them to be included in the copy by adding them as children of source issues.

  • Parent-child links are automatically created. Creating other types of links between copied issues is not currently supported.

  • All fields included in the source issues are copied to the new issues (as long as they are modifiable in the target project). An exception is the Reporter field: The user who performed the operation is assigned as the reporter instead of the original reporter.

Use Cases

Purpose

Action

Copy folders only

  • Filter the tree structure by the folder issue type (

in most cases “Folder”).Paste content to target

  • typically the type named “Folder”) - see Tree Filter and Search.

  • Select the desired folder in the filtered project tree.

  • Select Copy in the context menu.

  • Select the target folder in the same project tree

,

  • or in the tree of a different project

, and select

  • .

  • Select Paste in the context menu.

  • If the target is in a different project, select the option Create new issues in the Reuse Dialog.

  • Select

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

  • the other options as appropriate.

  • Select Paste.

Import

structure

folders and issues 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 folder or requirement in the project tree.

  • Select Copy in the context menu.

  • Select the target folder in the tree of 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

  • Select Paste in the context menu.

  • If the target is in a different project, select the option Import to tree In the Reuse Dialog.

  • Select the other options as appropriate.

  • Select Paste.

Copy folders and issues

  • Select a folder or requirement in the project tree.

  • Select Copy in the context menu.

  • Select the target folder in the same project tree or the tree of a different project.

  • Select Paste in the context menu.

  • If the target is in a different project, select the option Create new issues in the Reuse Dialog.

  • Select the other options as appropriate.

  • Select Paste.

Copy entire project tree into a new project

  • Create the new project

in Jira,

  • and activate it for

R4J

  • the use in easeRequirements.

  • Select

and copy

  • all the requirements and folders under the root folder of the

first

  • source project

Paste them to

  • .

  • Select Copy in the context menu.

  • Select 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

  • Select Paste in the context menu.

  • Select the option Create new issues in the Reuse Dialog.

  • Select the other options as appropriate.

  • Select Paste.