Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: REQ-16340

Overview

The reading view displays the items in a tree folder in a format designed for convenient reading. To access the view, select a folder or an issue in the tree and then select the Reading View icon.

Info

The reading view displays images inline, both in requirements and folders. You can attach images to requirements or folders and add links in their descriptions to achieve this.

Table of Contents

Operations

Open

detail

issue view

Select the issue key of a requirement to open the

detail

issue in its last selected view. If a requirement is included in multiple project trees

,

you can select one of

them is selected first

the projects.

Context menu

Right-click on a folder or issue header to show

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.

Configure Display Fields

See Display Fields

By default, the reading view displays the key, summary, and description of requirements. To add additional fields select the desired fields in the Display Fields dropdown 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 and description of requirements, as well as the description of folders, can be edited inline in the reading view

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 reading 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.