Date: Fri, 29 Mar 2024 06:37:35 +0000 (UTC) Message-ID: <741521417.3.1711694255909@1dadf4e77608> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2_221787447.1711694255907" ------=_Part_2_221787447.1711694255907 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The revision cleanup is a required action for this rele= ase. Read here for a c= omplete overview.
R4J 4.5 revision data is not compatible with older versions of R=
4J
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.
Known issue with MS SQL 2014/2016 databases. SQL Server= error encountered when executing revision cleanup: =E2=80=9CThe query proc= essor ran out of internal resources and could not produce a query plan...= =E2=80=9D.
This issue has been fixed in R4J 4.6.1, please upgrade your R4J version = if you are affected.
R4J 4.5.x will be the last version to support Jira 7 compatibili=
ty
From R4J 4.6.x onward, only Jira 8 will be supported. This is in line with&=
nbsp;Atlassian Support=E2=80=99s EOL Policy.
New features and improvements
Component |
Issue Key |
Summary |
|
---|---|---|---|
1 |
Revision History |
EASE-8390 |
Optimized handling of revision data; Fixed exponential growth of R4J rev= ision history table consuming a large percentage of database storage capaci= ty =E2=80=93 see Summary of functions affected by = revisions restructure in R4J 4.5. |
2 |
Administration: Cleanup Revisions |
Manual cleanup can be triggered by your Jir= a Administrator via App/Add-on Administration > (R4J section) Cleanu= p Revisions. However, please backup your data before performing the cl= eanup. 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.Hint: Project description will only be editable in Jira Project setti= ngs to ensure consistency in content format. |
4 |
Traceability View |
EASE-10562 |
Added support for sorting issues in traceability row and column when usi= ng JQL statement like =E2=80=9CORDER BY summary ASC=E2=80=9D in configured = view. |
5 |
Reuse |
EASE-11712 |
Added support for creating a link from source issue to reused linked iss=
ue. |
6 |
Reuse |
EASE-11646 |
Default field values configured shall be applied to the copied issue(s) = for fields which are not defined in =E2=80=9CFields to copy=E2=80=9C during= reuse. |
7 |
Custom Field: R4J Suspect |
REQ-9710 |
The new R4J Suspect custom field provides details on the changed issue a=
nd linked issue(s) affected. This information will show in the revision his=
tory. |
8 |
Revisions: Linked Issues |
REQ-10086 |
Added support for revisions of issue link changes; Linking and unlinking=
will show in the revisions. |
9 |
REST API: Field Blacklist |
REQ-10376 |
New REST API 2.0 endpoint to get, add, and remove fields from the R4J fi= eld blacklist =E2=80=93 see details in REST = API 2.0 Reference |
Bugfixes
Component |
Issue Key |
Summary |
|
---|---|---|---|
1 |
Tree View: Get URL |
EASE-11625 |
Fixed =E2=80=9CGet URL=E2=80=9C 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 colu= mn. |
5 |
REST API 1.0 |
EASE-11213 |
Fixed incorrect response for coverage /1.0/export/excel endpoint when =E2=80=9CfromColumn=E2=80=9D par= ameter other then 0 is requested. |
6 |
Administration: Logging |
EASE-11302 |
Fixed logging for groups deleted in Jira used in permission configuratio= n in R4J =E2=80=93 logging will be at INFO level instead of ERROR. |
7 |
Administration: Field Blacklist |
REQ-9614 |
Fixed field dropdown selector showing unsupported fields =E2=80=93 see <= a href=3D"/wiki/spaces/REQ4J/pages/1802731641/Field+Blacklist+Supported+Fie= lds" data-linked-resource-id=3D"1802731641" data-linked-resource-version=3D= "1" data-linked-resource-type=3D"page">Field Blacklist Supported Fields= for supported fields and field types. |
8 |
Reuse |
EASE-11842 |
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 =E2=80=9CCopy a= ttachments=E2=80=9C is set to Yes. |