DATA CENTER AND SERVER | CLOUD
Detail View
Overview
The requirement detail view displays the information about a requirement. The view is located on the right side of the project tree view and is visible if a requirement is selected in the project tree. Requirements are Jira issues, so the information in the detail view includes the same information in the standard Jira issue view, but also includes additional sections for features provided by R4J.
Each section in the detail view retains its expanded or collapsed state for folders and issues.
R4J Detail View Features
Section | Feature |
|---|---|
Child Requirements | This section lists the issue key and summary of the child requirements of the selected requirement. |
Issue Links | This section displays the links of the selected requirement and provides additional features for requirement management. The section also provides the Link Graph tool, which displays the selected requirement and its linked requirements as nodes in a graph, with links displayed as edges between the nodes. The nodes can be expanded and collapsed to reveal other linked requirements. When a link is marked as a suspect in the link section, additional options for evaluating the link become available. |
Revisions | This section displays the revisions of the selected requirement, including the revision number, timestamp, the user responsible for the changes and the changes themselves are displayed. A link to a list of baselines that include a revision is also provided. R4J provides the custom field "R4J Issue Revision", which your Jira administrator can add to screens so that it is visible to users. |
T4J Test Steps | When Test Management for Jira (T4J) is installed and the selected project is enabled for both R4J and T4J, the test steps section is displayed in the detail view. |
Operations
Child Requirements
Purpose | Action | Comment |
|---|---|---|
Create a new child issue |
|
|
Add an existing issue as child |
|
|
Reorder child requirements |
|
|
Remove a child requirement |
| This issue is unlinked from the parent issue, not actually deleted. |
Issue Links
Purpose | Action | Comment |
Create a new linked issue |
|
|
Add link |
| The dialog also allows linking the issue to a Confluence or web page. |
Modify link |
| The dialog allows you to change the link type or mark it as suspect. |
Unlink |
|
|
Compare with linked issue |
| See Comparison Tool. |
Show more links |
| By default at most five links are displayed. |
Open Link Graph |
| Select the Show Options link in the Link Graph to display the options for filtering the requirements displayed in the view. Here you can specify which issue types and link types are used to select the requirements to be shown, as well as the fields to display. Select the option Hide Link Types to remove the link labels from the graph. |
Review Suspect Link |
| These actions are only available for links flagged as suspect. |
Clear Suspect Flag |
|
Revisions
Purpose | Action | Comment |
|---|---|---|
Compare revisions |
| See Comparison Tool. |
View revision details |
| The dialog shows the selected revision’s details and the baselines in which it is included. |
Show more revisions |
| By default at most five revisions are displayed. |
Display Fields
There are fields that must be displayed in the detail view regardless of screen field configuration because they are intrinsic to requirements management. These fields are Status, Summary, Description, Attachment(s), Linked Issues. All of which are located in the header or as its own section in the detail view.
In the “Details“ section, multi-line fields are displayed using the full width of the detail view. The rest of the field types follow a two-column layout.
Screen Field Configuration Tabs
The “Details“ section displays selected essential fields in a fixed order regardless of screen field configuration. These essential fields are Path, Issue Type, Priority, Resolution, Assignee, Created, Updated, and Labels, respectively. Other fields are displayed according to their order in the view screen field configuration and only when they have a value.
View Screen | View Screen | R4J Detail View |
|---|---|---|
“Details“ section contains essential fields only. | ||
Single Tab | “Details“ section contains essential fields, followed by other fields in configuration | |
Multiple Tabs | “Details“ section contains essential fields only. A new section will be created for each tab, with the section name being the field tab’s name. Each section will be filled with the fields assigned to the corresponding tab. If all fields of a section do not have values, it will not be displayed. |
The R4J administrator maintains a so-called “blacklist” of fields that are not included in the R-4J Detail View but would be displayed in the standard Jira issue view. See Managing the Field Blacklist.
Inline Editing
The summary, description, and most fields under the “Details“ section of requirements and folders can be edited inline in the detail view.
While most fields have been verified as supporting inline editing, custom field types and fields coming from third-party vendors may not be editable.
Issue editing and field editing permissions, as well as Edit screen configurations, apply when inline editing. Read-only fields also remain un-editable. Changes applied to items in the detail view are saved automatically when navigating away from the field. Additionally, changes can be saved or cancelled explicitly through the Save and Cancel buttons.