#3308: Quire Feedback
Status: Completed
Tag: Wont Do

One of the core features of Quire is the independence of single tasks even if they are ordered in a hierarchy of a task-tree. This feels strange in the beginning but has many advantages as well. Sometimes it would be nice to have a choice to keep a task-tree as it is and do not mix it up by different sort views. This option should be available as a default setting for a project and should be changeable for every root-task-element like keep sub-tasks with root-task. When activated the tasks should always stay together and if some kind of sort selection is applied the whole task tree should match to the closes match within the whole task-tree. If the task-tree look like this:

  • Root-Task (due 4th) (normal prio)
    • Sub-Task (due 3rd) (low prio)
      • Sub-Sub-Task (no due) (high prio)
    • Another Sub-Task (due 5th) (normal prio)

The whole tree should be shown on the 3rd (as the Sub-Task is due an the 3rd) when sorted by date. The whole tree should be shown on a high prio selection as the Sub-Sub-Task has a high-prio.

What do you think?

Created by konsumschaf Jun 9, 2020, Edited Jun 16, 2020

@Uquire-998 - after some internal discussion, I'm afraid that we won't implement this feature request. We feel like keeping the tree structure when grouped/sorted loses the meaning of grouping/sorting. Also, it will probably make it more confusing if users are looking for tasks with a certain criteria (because the entire tree branch will probably be under another group/slot). Hope this makes sense. 😝

Peggy, Jun 16, 2020

@Uquire-998 - thank you for the explanation. I understand it clearly. I will pass your suggestion to the team and let you know if there's an update. 🙌

Peggy, Jun 12, 2020

Hi @peggy ,

Sorry, I did not explain my proposal good enough. My idea is to keep the whole tree in the slot that fits best, so in your example the whole tree would be shown in High and nothing in Normal or Low.

High:

  • Root-Task (due 4th) (normal prio)
    • Sub-Task (due 3rd) (low prio)
      • Sub-Sub-Task (no due) (high prio)
    • Another Sub-Task (due 5th) (normal prio)

Normal:

Low:

As soon as the high prio task is completed the whole tree should be moved to Normal:

High:

Normal:

  • Root-Task (due 4th) (normal prio)
    • Sub-Task (due 3rd) (low prio)
      • Sub-Sub-Task (no due) (high prio)
    • Another Sub-Task (due 5th) (normal prio)

Low:

I hope this helps.

konsumschaf, Jun 12, 2020

@Uquire-998 - just to double-check, do you mean, for example: when grouping by Priority, you would like to see the same task tree in each group?

High

  • Sub-Sub-Task (no due) (high prio)

Normal

  • Root-Task (due 4th) (normal prio)
    • Sub-Task (due 3rd) (low prio)
      • Sub-Sub-Task (no due) (high prio)
    • Another Sub-Task (due 5th) (normal prio)

Low

  • Root-Task (due 4th) (normal prio)
    • Sub-Task (due 3rd) (low prio)

Personally, I think it's kind of weird and confusing for me to see a NORMAL priority task in the Low Group... 😭

Peggy, Jun 12, 2020