Summary | Parent task make sort by date impossible |
Queue | Nag |
Queue Version | Git master |
Type | Enhancement |
State | Rejected |
Priority | 2. Medium |
Owners | |
Requester | samuel.wolf (at) wolf-maschinenbau (dot) de |
Created | 03/17/2014 (4233 days ago) |
Due | |
Updated | 01/27/2016 (3552 days ago) |
Assigned | |
Resolved | 01/27/2016 (3552 days ago) |
Milestone | |
Patch | No |
State ⇒ Rejected
about the sort being incorrect, it's about not being able to choose
to sort on the desired column. I.e., the link to initiate the date
sort isn't working.
change in the GUI.
./nag/list.php?sortby=due&sortdir=0
./nag/list.php?sortby=estimate&sortdir=0
./nag/list.php?sortby=assignee&sortdir=0
after some invenstigation, I think I understand how Samuel reached
his situation where sorting is not working.
I think it is partly explained by the case described in
ticket 14138.the sort being incorrect, it's about not being able to choose to sort
on the desired column. I.e., the link to initiate the date sort isn't
working.
See comment
#3.after some invenstigation, I think I understand how Samuel reached his
situation where sorting is not working.
I think it is partly explained by the case described in
ticket 14138.If you define these tasks (2 parents, 2 childs):
P1
+-- C1
P2
+-- C2
and then you sort, then effectively only P1 and P2 get sorted
depending on the column you select (Priority, Date, name, ...). Works
great. And nobody complains about the sorting as it is logical that
child tasks are not sorted by their attributes but rather by their
parent.
But Samuel said he had a lot of jobs. Thus, he uses labels to group
them, and he filters by label. Thus, as mentioned in
ticket 14138, therelationships between P1 and C1, and between P2 and C2 is still there
but no longer shown.
Thus, when you now sort, it seems as if the sorting does not work: the
same sequence appears as before, but the indentation and the parent to
child lines are gone. So you just get a flat list, and sorting seems
to be broken.
Samuel,
can you confirm that you use label filtering when this behaviour occurs?
But there is an easy work arround for Samuel:
When you create a Smart list (via the search option, and select to
save your query as a smart list) with the label(s) selected, then, in
the current implementation, the output of that smart list forgets all
parent to child relationships and thus sorting works again the native
way: each task gets sorted by its value, disregarding any parent or
child relationship.
I'm not sure this is the desired way of working, but that is how it
works on version 4.2.5 of nag.
Regards,
Xavier
horde 5.2.3 stable
nag 4.2.3 stable
horde 5.2.3 stable
nag 4.2.3 stable
I can sort by any column I desire when subtasks are displayed.
New Attachment: tasks_example.png
List" column.
Delete the "subtask1" and _all_ columns can sort again (it is not only
a date column problem).
State ⇒ Feedback
Version ⇒ Git master
and have many task hierarchies. Of course we keep the hierarchy even
if sorting by date, otherwise it would be impossible to track related
tasks.
Priority ⇒ 2. Medium
State ⇒ New
Patch ⇒ No
Milestone ⇒
Queue ⇒ Nag
Summary ⇒ Parent task make sort by date impossible
Type ⇒ Enhancement
Maybe it is possible to sort only for normal task and do not watch
about the "partens tasks"?
Another idea?
It is nearly impossible to sort our really long task list now.