DATA CENTER AND SERVER | CLOUD
4.16
Elevated user experience
Increased flexibility in configuring display fields through a new design.
Inline editing support for custom fields, ensuring consistency with Jira's display in the detail and reading view.
More intuitive context menu for reading view and tabular view.
These enhancements make it easier for users to customize their display fields and interact with the system more efficiently.
Component | Issue Key | Summary | |
|---|---|---|---|
| 1 | The new display fields selector A new display fields selector has been implemented for the tree view, reading view, tabular view, and baseline view as a dialog transfer input instead of a multi-select dropdown. Other areas not mentioned retain the display fields multi-select dropdown. The new implementation offers the following advantages:
Note that fields available for display in the reading and tabular view are retrieved from the projects' view screen configurations. For the tree, only system default fields are supported. More custom fields and icons will be available in future releases. | ||
| 2 | Display fields: Tree view | EASE-9151 EASE-9151 | New! Customize the information you want to see in your tree hierarchy. It’s no longer limited to just the priority icon, issue key, and summary. Basic system fields can be shown for issues on the tree too. We’ve also moved the Tree Setting for “Auto numbering for tree folders” to the tree display fields configuration. Hint: To configure, right-click on the tree’s root project folder and select Configure display fields in the context menu. |
| 3 | Display fields: Reading view and Tabular view | EASE-8313 EASE-8313 | Save a different set of display fields for your reading view and tabular view! The fields between these views are now independently persisted.
|
| 4 | REQ-14886 | Select fields to be displayed for issues and folders in the reading view. | |
| 5 | Display fields: Baselines | EASE-8392 | Fields saved as display fields that are not in the current baseline being viewed will be shown in the selected display field with a warning. |
| 6 | REQ-15188 | Summary fields can no longer be configured as a display field, instead it is a fixed field in the baseline views to ensure that the baseline views are not mistakenly perceived as empty. | |
Other features and improvements
Component | Issue Key | Summary | |
|---|---|---|---|
| 1 | Inline editing: Detail view and reading view | EASE-8122 EASE-8122 | Increase your productivity by making all modifications inline in R4J’s detail view and reading view – including custom fields! Note that some 3rd-party plugin custom fields may remain unsupported depending on the vendor’s implementation. Jira administrators can enable/disable inline editing capabilities in R4J by setting “Allow inline editing“ permissions. |
| 2 | General: Navigation | EASE-12672 EASE-12672 | Open an issue in Jira issue view directly from the issue key. Click on the link icon that shows on the top right of an issue key link on hover. |
| 3 | Context menu: Reading view and Tabular view | EASE-15062 | Access a context menu of available operations from the reading and tabular view by clicking on the ellipsis (…) on the left side of an issue key in the view. |
| 4 | Configuration: Coverage formula | EASE-12610 | Configure the formula you want to apply to your coverage view: row-based or issue-based. Read more |
Bugfixes
Component | Issue Key | Summary | |
|---|---|---|---|
| 1 | Word export | EASE-17150 | Fixed Word export template using .docm extension not working. |
| 2 | Word export | EASE-16686 | Fixed incorrect page number in Word export. |
| 3 | Jira issue view: Requirements tab | EASE-17286 | Fixed child requirements always showing as "Open" status regardless of actual status. |
| 4 | Integrity check: Revisions | EASE-16410 EASE-16410 | Extended existing baseline integrity check to fix discrepancy between issue history and revision comparison for project. |
| 5 | Coverage view | EASE-17105 | Fixed issue where the whole coverage view is exported in XML and Excel even when filtered. |
| 6 | Detail view | EASE-17223 | Fixed attachments not showing if “Attachment“ is not in field configuration or if the field is blacklisted. |
| 7 | Traceability view | EASE-17134 | Fixed view scrolling upward after clicking the add link icon in the matrix. |
| 8 | Reading view | REQ-15097 | Fixed pages in reading view reloading unnecessarily. |
| 9 | REST API 1.0 | REQ-15100 | Fixed user permission checking for getting private coverage views. |