4.5.0

The revision cleanup is a required action for this release. Read here for a complete overview.

Update Oct 1, 2021:
Known issue with MS SQL 2014/2016 databases. SQL Server error encountered when executing revision cleanup: “The query processor ran out of internal resources and could not produce a query plan...”. Investigation and fix is ongoing. If you are encountering this issue, please contact us through our support portal.

R4J 4.5 revision data is not compatible with older versions of R4J
From R4J 4.5, the change sets are evaluated based on issue field values in Jira history, we no longer store issue field values in R4J revision tables which will cause revisions created in R4J 4.5 to show as empty change sets in older versions.

R4J 4.5.x will be the last version to support Jira 7 compatibility
From R4J 4.6.x onward, only Jira 8 will be supported. This is in line with Atlassian Support’s EOL Policy.

New features and improvements

Component

Issue Key

Summary

Component

Issue Key

Summary

1

Revision History

EASE-8390

EASE-8490
EASE-9231
EASE-9784
EASE-10551
EASE-10556
EASE-11086
EASE-11352
EASE-11353
EASE-11482

Optimized handling of revision data; Fixed exponential growth of R4J revision history table consuming a large percentage of database storage capacity – see Summary of functions affected by revisions restructure in R4J 4.5.

2

Administration: Cleanup Revisions

Manual cleanup can be triggered by your Jira Administrator via App/Add-on Administration > (R4J section) Cleanup Revisions. However, please backup your data before performing the cleanup. We strongly recommend that you first run and verify the result on a staging system.

3

Administration: Tree View

EASE-11401
EASE-11474

Modified behavior when editing root project folder description in R4J.
Hint: Project description will only be editable in Jira Project settings to ensure consistency in content format.

4

Traceability View

EASE-10562
EASE-11497

Added support for sorting issues in traceability row and column when using JQL statement like “ORDER BY summary ASC” in configured view.

5

Reuse

EASE-11712

Added support for creating a link from source issue to reused linked issue.
Tip: In reuse configuration, set both “Create links to new issues” and “Copy directly linked issues” to Yes with selected link type.

6

Reuse

EASE-11646

Default field values configured shall be applied to the copied issue(s) for fields which are not defined in “Fields to copy“ during reuse.

7

Custom Field: R4J Suspect

REQ-9710

The new R4J Suspect custom field provides details on the changed issue and linked issue(s) affected. This information will show in the revision history.
Tip: If unwanted, please include R4J Suspect in the field blacklist.

8

Revisions: Linked Issues

REQ-10086

Added support for revisions of issue link changes; Linking and unlinking will show in the revisions.
Tip: If unwanted, please include Linked Issues in field blacklist.

9

REST API: Field Blacklist

REQ-10376

New REST API 2.0 endpoint to get, add, and remove fields from the R4J field blacklist – see details in REST API 2.0 Reference

Bugfixes

Component

Issue Key

Summary

Component

Issue Key

Summary

1

Tree View: Get URL

EASE-11625
EASE-11680

Fixed “Get URL“ not persisting selected item when shared.

2

Word Export

EASE-11128

Fixed rendering of numbered lists inside tables.

3

ReqIF

EASE-11169

Fixed importing error for manually compressed ReqIF files (reqifz format).

4

Coverage View

EASE-11413

Fixed error when using Epic Name or Epic Links to order issues in a column.

5

REST API 1.0

EASE-11213

Fixed incorrect response for coverage /1.0/export/excel endpoint when “fromColumn” parameter other then 0 is requested.

6

Administration: Logging

EASE-11302

Fixed logging for groups deleted in Jira used in permission configuration in R4J – logging will be at INFO level instead of ERROR.

7

Administration: Field Blacklist

REQ-9614

Fixed field dropdown selector showing unsupported fields – see Field Blacklist Supported Fields for supported fields and field types.

8

Reuse

EASE-11842
REQ-10204

Fixed issues with sub-tasks not showing in tree after reuse.

9

Reuse

REQ-10320

Fixed reuse only copying one out of multiple issues when “Copy attachments“ is set to Yes.