Sort by date to include subtasks (Suggestion)

[Matthew Reischer]

Hi,
Sometimes I have a a task with no due date, but one or more of it's subtasks has a due date.
It would be great if the earliest date of a subtask would inherit to the parent task for sorting and visibility purposes.

The subtask would display "Jul 25", the parent task (if there was no date) would display "(Jul 25)" which would be the least or all due dates for that task and it's subtasks.

Thanks!



Sorting with the parent task visible and subtasks hidden would use this "inherited" date.

Hope that makes sense.

[Cameron (GQueues Team)]

Thanks for the feedback, Matthew.  I understand what you are describing.  It seems like it might be fairly complex to implement, but we'll consider it as a possible enhancement.

-Cameron

--
You received this message because you are subscribed to the Google Groups "GQueues Discussion Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gqueues+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqueues/715964fb-8b03-4c46-8878-1560c87541ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Cameron Henneke

Founder, GQueues

"The leading Google-integrated task management service for people and teams."

[Matthew Reischer]

Hi Cameron,

Right now, I have promote the subtask so that it sorts as a top level task.

That could be OK, but the parent task and subtask lose their context, If the promoted subtask is "Call Joe", I may no longer know which Joe or why. If there is another subtask to follow in sequence, that information is lost as well.

I understand that a solution may be difficult to implement.  Each task would need new internal fields like "greatest sort date", "least sort date" in addition to the existing due date, and you would have to modify the sort routines to utilize the new fields. The search routine should be OK as is.

I always sort by date in ascending order.  If you can make that assumption, it will simplify the job greatly.  It might be worth doing that and wait to see if anyone complains (agile development?)

That would mean you can have field "display date" which is the lesser of the the dates of a task and its children and has an unambiguous definition.  That could be displayed where the current date is, but perhaps with font change or parens() to indicate it is inherited.

Of course you would also need triggers to update the "display date" whenever a subtask is modified.  If you don't have that available, it will be tough.

Anyway, thanks for considering this and you can file this email however you please...

Matthew Reischer, MSME
Northeastern Energy Consultants
Voice 856-448-4069
Fax 866-670-4065
MRei...@neecons.com

www.neecons.com

@matt_reischer (Twitter)

LinkedIn

--
You received this message because you are subscribed to a topic in the Google Groups "GQueues Discussion Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gqueues/UuyguL_lPQI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gqueues+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gqueues/CAJtDqkR1ufpbbutKvH1ho%2BhwSKhNvDhD7QQprLpGczxDgTQO4Q%40mail.gmail.com.