CLOUD | DATA CENTER AND SERVER
Project Tree View
Overview
The Project Tree View is reached by selecting an activated project from the Jira projects in the main navigation bar and then selecting the item “Requirements Management for Jira” in the project sidebar. This opens the R4J sidebar, where you then select Tree. The project tree replaces the R4J sidebar.
The tree is located on the left side of the view and can be collapsed. Selecting a folder or requirement in the project tree opens the Detail View for the item on the right side. For folders, switch to the Reading View by clicking on the reading view icon in the project tree sidebar.
The requirements of a given project can only appear once in its tree. However, since requirements in one project may be reused in other projects, they may appear in multiple project trees.
Requirements may be included in other requirements as child requirements. Child requirements are manipulated in exactly the same ways as other requirements and may be indefinitely nested.
Folders are also Jira issues. The items in a folder are treated as child requirements of the folder.
Jira subtasks are not automatically displayed as children of their parent issues in the project tree. If this is desired, they can be added as child requirements of their respective parents.
Context Menu Operations
The project tree consists of the project folder and issues. To access the context menu, right-click on any item in the tree. Each type of item has its own set of context menu entries for performing appropriate operations, as indicated in the following tables.
Availability | |||||
Project | Folder | Issues | Multi-select | ||
|
|
| Edit | Opens the Jira Edit Issue dialog. Close the dialog to see the updated requirement in the tree. | |
Compare Issue | Opens the Issue comparison dialog, to allow users the ability to compare and copy values of issues with other issues. | ||||
|
|
|
| Create issue/folder | Opens the Jira Create Issue dialog. Select Create to create the new folder or requirement. |
Create baseline | Opens the Baseline Create dialog, which allows you to create baseline for your requirements. | ||||
|
|
|
| Create child issue | Opens the Jira Create Issue dialog. Select Create to create the new child requirement. |
|
|
|
| Create linked issue | Opens the R4J Create Linked Issue dialog, which allows you to specify the outgoing link type, the project in which the new issue should be created, the issue type of the new issue, and if the issue should be added as child of the selected issue. Selecting Create opens the Jira Create Issue dialog, prefilled with the information entered in the R4J Create Linked Issue dialog. Select Create to create a new issue of the chosen type in the chosen project, linked to the new issue with the chosen link type. |
|
|
|
| Add existing issues | Opens the R4J Add Existing Issues dialog, where the following options are available:
You may also create a link from the selected requirement to the added requirements from the dialog. Due to the fact that issues may only appear once in a project’s tree, any issues that are already in the tree are ignored even if they match a filter or are manually selected to be added. |
|
|
|
| Add link | Opens the R4J Add Link dialog, which allows you to add a link to an existing Jira issue or Web link to the selected issue. Select Link to link the selected issues. |
|
|
|
| Show in issue navigator | Displays all the issues that are under the selected parent in the Jira issue navigator. |
|
|
|
| Export | Exports data using Word Template based Export. |
|
|
|
| Copy | Stages one or more requirements for copying within the same project or to a different project (also known as Requirements Reuse). |
|
|
|
| Paste | When copied items are pasted (reused), users are given an option to create/import the issue in the target project. Newly created folders and issues are inserted into the project tree. The fields of the created entries get the values copied from the source issues, depending on field settings of the target project. Issue links between the source and target issue can be created depending on the link type selected on the reuse dialog. |
|
| Remove | Opens the Remove Issue dialog. Select Remove to confirm removal of the issue in the tree. Removing issues from the tree will remove all its child issues recursively. Issues will not be deleted in Jira and can be added again to the tree. | ||
Display Fields | Opens the Display Fields dialog. Display Fields allows you to set what field values you want to be displayed in the R4J Tree. Project administrators can save default fields for specific issue types for normal users to use as reference. When user is logged in as a project administrator, button “Save as project default“ is displayed in the lower left of the dialog. | ||||
Expand and Collapse
Click on the arrows on the left-side of the tree item icon to expand or collapse the hierarchy.
Expanding an item only expands items directly under it
Collapsing an item closes all items under it recursively
Drag and Drop Operations
The project tree supports the following drag and drop operations:
Change the position of requirements
Create and remove child requirements
Move child requirements to other parents
Tree Filter and Search
R4J offers two options to find interesting details in the tree: The search option highlights all matching Jira issues, the filter options reduces the tree to the queried items.
To filter the issues in the project tree, select the Filter Tree icon above the tree. To search for relevant issues, select the Search in Tree icon next it.
Both option supporting following modes:
Text: Enter text in the input field use a full text search of the requirements in the project tree.
Advanced: Displays a dialog where a user can search using JQL, Jira Filter or using Jira field values.
To use this option, click the “Advanced” option in the search/filter bar.