We are proud to announce our R4J - Requirements Management for Jira will release version 4.5 soon.
If you would like to participate in the 4.5 BETA release, we advice for you to prepare the following ahead of the release:
A test instance (Most preferably one that has close to production data)
A backup of your test instance data – the revision cleanup process cannot be aborted and can only be reverted through a backup
The revision cleanup process is a required action for this release. Due to the clearing up of data in the R4J revision history tables, views that use the revisions are affected and were modified accordingly to fit the new implementation. The cleanup is performed as a background task and no downtime is expected.
Known issues
R4J 4.5 is not backward compatible with older versions
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.
Issue comparison request failure for reactivated projects from lower versions (affected versions: R4J 1.6 to 4.4.2)
This issue will be fixed before 4.5 official release.
Issues from projects that were activated, generated with revisions, deactivated, then reactivated will experience request failure in issue comparison with the latest beta build version #41.
New features and improvements
Component | Issue Key | Summary | |
---|---|---|---|
1 | Revision History | EASE-8390 | 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 | Modified behavior when editing root project folder description in R4J. |
4 | Traceability View | EASE-10562 | 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-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. |
6 | Word Export | REQ-10243 | Updated Apache POI dependency from 3.16 to 4.1.2. |
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. |
8 | Revisions: Linked Issues | REQ-10086 | Added support for revisions of issue link changes; Linking and unlinking will show in the revisions. |
Bugfixes
Component | Issue Key | Summary | |
---|---|---|---|
1 | Word Export | EASE-11751 | Fixed error 500 “NoClassDefFoundError“ of class |
2 | Coverage Statistics Gadget | EASE-11683 | Fixed coverage statistics gadget not loading. |
3 | Tree View: Get URL | EASE-11625 | Fixed “Get URL“ not persisting selected item when shared. |
4 | Word Export | EASE-11128 | Fixed rendering of numbered lists inside tables. |
5 | ReqIF | EASE-11169 | Fixed importing error for manually compressed ReqIF files (reqifz format). |
6 | Coverage View | EASE-11413 | Fixed error when using Epic Name or Epic Links to order issues in a column. |
7 | Traceability View | EASE-11595 | Fixed pagination for saved traceability views. |
8 | REST API 1.0 | EASE-11213 | Fixed incorrect response for coverage /1.0/export/excel endpoint when “fromColumn” parameter other then 0 is requested. |
9 | 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. |
10 | Administration: Field Blacklist | REQ-9614 | Fixed field dropdown selector showing unsupported fields – see Field Blacklist Supported Fields for supported fields and field types. |
11 | Reuse | REQ-10204 | Fixed issues with sub-tasks not showing in tree after reuse. |
12 | Reuse | REQ-10320 | Fixed reuse only copying one out of multiple issues when “Copy attachments“ is set to Yes. |