MantisBT - v3.2 Release
View Issue Details
0001055v3.2 ReleaseReportspublic2012-02-10 11:252014-07-16 21:28
Reporterjrhall 
Assigned Tocaseydk 
PrioritynormalSeverityminorReproducibilitysometimes
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version3.2Fixed in Version3.2 
Summary0001055: Task List Report sorting error
DescriptionWhen requesting a task list report, one parent task is appearing at the bottom of the list of its child tasks. This causes the first child to appear to be a child of the wrong task.

I have attempted changing capitalization, updating the parent task, adjusting task status, etc., but am unable to reproduce the error with another task.
TagsNo tags attached.
has duplicate 0001464closed caseydk Pending Requests tasklist orders by date, not parent/date 
Attached Filespng Report - Task List - Bad Sort.png (11,630) 1969-12-31 16:00
https://bugs.web2project.net/file_download.php?file_id=316&type=bug
png

png Report - Task List - Bad Sort - follow-up.png (18,924) 1969-12-31 16:00
https://bugs.web2project.net/file_download.php?file_id=340&type=bug
png

csv tasks.csv (2,083) 1969-12-31 16:00
https://bugs.web2project.net/file_download.php?file_id=341&type=bug

Notes
(0002486)
robertbasic   
2012-04-20 05:18   
jrhall, could you please mark/write down somehow what should be the correct order of the tasks?

thanks!
(0002491)
jrhall   
2012-04-20 13:23   
robertbasic,

I've attached another image ("Report - Task List - Bad Sort - follow-up.png") that shows a little more detail. ...Not sure why I didn't use this image in the first place.

The task "SELECT DATES AND VENUES" is the parent task for the other two tasks in the "On Campus Trainings" project. It should, in theory, appear before either of the other child tasks "DATES AND VENUE COMPLETION" and "Determine Blackout Dates for TSC REED" - that would also match with the visual hierarchy that it's trying to draw.

In doing some more checking just now, I realized that "DATES AND VENUE COMPLETION" was a milestone. However, when I convert it to a regular task, the problem persists.

Also interesting - the sort order matches the order in which they are appearing in the unsorted "tasks" database table, once you account for the initial grouping by project. Since the application is still in the pre-use phase on our end with nothing but testing tasks, I'll also upload a CSV of my tasks table in case that's of any help.
(0002671)
caseydk   
2012-10-28 17:53   
The key to reproducing this one is having sub and dynamic tasks along with others that overlap. Depending on their dates, they can easily come up out of order.

Since this is just annoying and only exists in the Reporting, I'm going to move this to Post-v3.0 development.
(0003277)
caseydk   
2014-03-30 21:57   
This was resolved in v3.2 development. Latest tweak is here:
https://github.com/web2project/web2project/commit/0bd0436d6a760be84c2ceeeaf7b90b325de24393

Issue History
2012-02-10 11:25jrhallNew Issue
2012-02-10 11:25jrhallFile Added: Report - Task List - Bad Sort.png
2012-04-20 05:18robertbasicNote Added: 0002486
2012-04-20 13:10jrhallFile Added: Report - Task List - Bad Sort - follow-up.png
2012-04-20 13:23jrhallNote Added: 0002491
2012-04-20 13:23jrhallFile Added: tasks.csv
2012-04-21 19:07caseydkProjectv2.4 Release (Closed) => v3.0 Release
2012-08-07 21:10caseydkStatusnew => assigned
2012-08-07 21:10caseydkAssigned To => caseydk
2012-10-28 17:50caseydkReproducibilityunable to reproduce => sometimes
2012-10-28 17:50caseydkProduct Version2.4 =>
2012-10-28 17:53caseydkNote Added: 0002671
2012-10-28 17:53caseydkProjectv3.0 Release => Pending Requests
2014-02-27 00:29caseydkRelationship addedhas duplicate 0001464
2014-02-27 00:29caseydkProjectPending Requests => v3.2 Release
2014-03-13 22:17caseydkTarget Version => 3.2
2014-03-30 21:57caseydkNote Added: 0003277
2014-03-30 21:57caseydkStatusassigned => resolved
2014-03-30 21:57caseydkResolutionopen => fixed
2014-04-05 17:30caseydkCategoryGeneral => Reports
2014-07-16 21:26caseydkFixed in Version => 3.2
2014-07-16 21:28caseydkStatusresolved => closed