Overview
Operations
Open issue view | Select the issue key of a requirement to open the issue in its last selected view. If a requirement is included in multiple project trees you can select one of the projects. |
Context menu | Click on the ellipsis on the left side of the issue key in the issue key column to see available operations in the context menu, which provides the same options provided in the tree view. See https://easesolutions.atlassian.net/wiki/spaces/REQ4J/pages/1379991806/Project+Tree+View#Context-Menu-Operations. |
Display Fields
By default, the reading view displays the key, summary, and description of requirements; and the numbering, summary, and description of folders. To add additional fields, click on the Display Fields button, select desired fields from the available fields, and confirm the selection with the Display button. The selection of fields is saved for the user and applied from now on.
Since the reading view may display issues from various projects with different fields and permission schemes, values for fields with project-specific permission restrictions or which do not exist for some issues are not displayed.
Editing
The summary, description, and most fields under the “Details“ section of requirements and folders can be edited inline in the reading view. Note that, while most fields have been verified, custom field types and fields coming from third-party vendors may or 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 by setting “Allow inline editing“ permissions.