easeRequirements Detail View Features
Section | Feature | Child Requirements||||
---|---|---|---|---|---|
| This section lists the issue key and summary of the child requirements of the selected requirement. Issue Linksdisplays the Review sub-tasks necessary to execute a review of requirements. See Review Cockpit. This section is only available for the detail view of issue types configured as a Review issue in the Review Scheme associated with the selected project. | ||||
| This section displays the UML diagrams created for the requirement. See UML Diagrams. | ||||
Linked Issues | This section displays the links, issue key and summary of the child requirements 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. View all link entries in one unified link table. The following sections in older versions have been merged where different link operations are available based on the origin.
| ||||
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 easeRequirements provides the custom field "R4J easeRequirements 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) easeTest is installed and the selected project is enabled for both R4J easeRequirements and T4JeaseTest, the test steps section is displayed in the detail view of test case issues. |
Operations
Child RequirementsLinked Issues
Purpose | Action | Comment |
Open Link Graph |
|
Complete the Create Issue dialog.
Select Create.
Add an existing issue as child
| 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. |
Add link |
|
|
|
|
|
Purpose
Action
|
Reorder child requirements
Either drag the child requirement up and down or hover on the child requirement and then use the up and down arrows.
Remove a child requirement
Hover on the requirement and then select the delete icon.
Select Unlink in the Unlink Child Issue dialog.
This issue is unlinked from the parent issue, not actually deleted.
Issue Links
The dialog also allows linking the issue to a Confluence or web page. Issue link types may be restricted if there is a Data Model active for selected project. | |
Create a new linked issue |
|
|
| Issue link types may be restricted if there is a Data Model active for selected project. |
Add |
an existing issue as child |
|
| |
Create a new child issue |
|
|
|
Compare with linked issue |
| This action is available for an issue link with LINK origin. See Comparison Tool. |
Modify link |
|
| This action is available for an issue link with LINK origin. The dialog allows you to change the link type or mark it as suspect. |
Unlink |
|
|
Review Suspect Link
Select Review to review the changes that caused the link to be flagged as suspect.
These actions are only available for links flagged as suspect.
Clear Suspect Flag
|
Compare with linked issue
Select Compare on an issue to open the Comparison Tool.
See Comparison Tool.
Show more links
Select Show ... more links to display any links that are not displayed.
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.
This action is available for an issue link with LINK origin. | ||
Review Suspect Link |
| This action is available for an issue link flagged as suspect with LINK origin. |
Clear Suspect Flag |
| This action is available for an issue link flagged as suspect with LINK origin. |
Remove Confluence Page |
| This action is available for a Confluence page with LINK origin. |
Remove Web Link |
| This action is available for a web link with LINK origin. |
Remove a child requirement |
| This action is available for a child issue with TREE origin. This issue is unlinked from the parent issue, not actually deleted. |
Convert sub-task to issue |
| This action is available for a child issue with SUB-TASK origin. |
Remove from Epic |
| This action is available for a child issue with IN EPIC origin. |
Show more links |
| By default at most five entries are displayed. |
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 easeRequirements 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 easeRequirements 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.
Jira administrators can enable/disable inline editing capabilities in R4J easeRequirements by setting “Allow inline editing“ permissions.