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.
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.
New features and improvements
See all issue keys...
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.
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.
Administration: Tree View
Modified behavior when editing root project folder description in R4J.
Added support for sorting issues in traceability row and column when using JQL statement like “ORDER BY summary ASC” in configured view.
Added support for creating a link from source issue to reused linked issue.
Default field values configured shall be applied to the copied issue(s) for fields which are not defined in “Fields to copy“ during reuse.
Custom Field: R4J Suspect
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.
Revisions: Linked Issues
Added support for revisions of issue link changes; Linking and unlinking will show in the revisions.
Tree View: Get URL
Fixed “Get URL“ not persisting selected item when shared.
Fixed rendering of numbered lists inside tables.
Fixed importing error for manually compressed ReqIF files (reqifz format).
Fixed error when using Epic Name or Epic Links to order issues in a column.
REST API 1.0
Fixed incorrect response for coverage /1.0/export/excel endpoint when “fromColumn” parameter other then 0 is requested.
Fixed logging for groups deleted in Jira used in permission configuration in R4J – logging will be at INFO level instead of ERROR.
Administration: Field Blacklist
Fixed field dropdown selector showing unsupported fields – see Field Blacklist Supported Fields for supported fields and field types.
Fixed issues with sub-tasks not showing in tree after reuse.
Fixed reuse only copying one out of multiple issues when “Copy attachments“ is set to Yes.