This issue has been created
There are 2 updates.
 
 
Release Notes Application / cid:jira-generated-image-avatar-0d3f3706-dca0-488a-8df8-73a46e0d8b67 RN-95 Open

The Release Changes Live Data of the home page is not sorted by creation date any more

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-e84025cc-8456-47f1-ab7d-daeee051552f Vincent Massol created this issue on 31/Aug/26 19:25
 
Summary: The Release Changes Live Data of the home page is not sorted by creation date any more
Issue Type: cid:jira-generated-image-avatar-0d3f3706-dca0-488a-8df8-73a46e0d8b67 Bug
Affects Versions: 2.4
Assignee: Unassigned
Components: Application
Created: 31/Aug/26 19:25
Fix Versions: 2.6
Labels: usability
Priority: cid:jira-generated-image-static-major-e09ecbf4-ee33-442e-b488-60b35a1193c3 Major
Reporter: Vincent Massol
Description:

Problem

The "Release Changes" Live Data of the release notes home page (ReleaseNotes.Code.HomeReleaseChanges) has no default sort, so the rows are returned in whatever order the query produces them and the most recently created changes are not the ones the reader sees first.

Until RN-75 replaced the LiveTable with a Live Data, the #livetable macro picked a default sort column by itself (the first non special column of the column list, i.e. doc.creationDate). The liveData macro does not pick one, and no sort parameter was passed when the list was converted: the "Release Notes" Live Data of the same page got one (sort="date:desc"), the "Release Changes" one did not.

Proposal

Pass sort="doc.creationDate:desc" to the liveData macro, so that the changes added last are listed first, which is what a reader of that list is looking for. The doc.creationDate column is hidden by default (see RN-85) but that only affects its display: it is still part of the query and can be sorted on.

 
 

2 updates

 
cid:jira-generated-image-avatar-e84025cc-8456-47f1-ab7d-daeee051552f Changes by Vincent Massol on 31/Aug/26 19:25
 
Fix Version: 2.5.1
Assignee: Vincent Massol