[TASKS-35] Sorting tasks list by date column results in wrong order Created: 24/May/21  Updated: 18/Jun/23  Resolved: 13/Jun/23

Status: Closed
Project: Tasks
Component/s: None
Affects Version/s: 6.2.23
Fix Version/s: 6.3.0, 6.2.24

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Antonín Juran
Resolution: Fixed Votes: 3
Labels: Nucleus_AuthX_Support
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 0.25d Time Spent: 0.25d
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Problem/Incident
Relates
relates to MGNLUI-6400 Date column with large number of item... Closed
causality
Sub-Tasks:
Key
Summary
Type
Status
Assignee
TASKS-48 Implementation Sub-task Completed Antonín Juran  
TASKS-49 Code review Sub-task Completed Adam Siska  
TASKS-50 Pre-integration QA Sub-task Completed Adam Siska  
TASKS-51 Final QA Sub-task Completed Quach Hao Thien  
Template:
Acceptance criteria:
Empty
Release notes required:
Yes
Date of First Response:
Epic Link: AuthorX Support
Sprint: Nucleus 38
Story Points: 3
Team: AuthorX
Work Started:
Approved:
Yes

 Description   

Steps to reproduce

  1.  Import tasks from the attached files
  2. Open tasks app (tab all)
  3. Apply descendent order in column last change

Expected results

Tasks are correctly ordered by date

Actual results

At the bottom of the list, tasks from 2020 and 2021 are mixed

Development notes

During our tests, we observed the issue does not occur in one of our local environments. Libs, Java version, OS and Tomcat version are just the same than the rest of environments that reproduce the issue.



 Comments   
Comment by Jörg Wirsig [ 15/Nov/21 ]

I also noticed that bug, but after cleanup of all old tasks (deleted all tasks via JCR older than 2021-06) the issue does not longer exist. I guess it is an issue of large data amount and / or has something todo with older entries in multiple subfolders in JCR.

Comment by Ingo Hofmann [ 02/Mar/23 ]

We are facing the same issue in all environments. Also with a list of "only" 200 tasks. The order seems to be completely random and it prevents looking up recent publications.

Comment by Antonín Juran [ 01/Jun/23 ]

DISCOVERY

Last change column is configured with modificationDate in tasks-app.yaml (it corresponds to Task#modificationDate which is mapped to mgnl:lastModified node property in JCR). modificationDate is used in ORDER BY clause when sorting the column but such a property doesn't exists in JCR.

Suggested solution

Rename modificationDate column to mgnl:lastModified and adapt TasksPropertySetFactory as here. It could be done analogically also for creationDate column.

Generated at Mon Feb 12 11:03:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.