Sort by modified date (aka 'last update')
It would be really helpful to have a 4th sort option within a list, to sort by modified date (aka 'last update'). This could apply only to the parent task level so that any details under that task would retain the custom order set by the user. Or have the option to apply the sort to 1, 2, or 3 levels deep to accommodate more working styles (even better).
This would also add consistency to the experience since the lists themselves already support sorting by last update (both on the homepage and in the list navigation menu at the top of the screen from any list).
Sample use case:
Cranking on a project that's been broken into many smaller chunks. Any chunks being actively worked on would be at the top while the less active chunks would automatically sink toward the bottom of the list. This gets the less active chunks out of the way, but also signals that they haven't been worked on in a while (both provide helpful visual feedback).
Why this solves an important issue:
I often stop using Checkvist for large projects because it becomes too rigidly structured, making it hard to quickly capture changing requirements, tasks, etc. without having to place them in just the right spot in the structure. I'd rather have the option to capture these items in a fluid way and have them sort by modified date (at the 1st and/or maybe 2nd level) while still retaining structure within the details and subtasks. It would create a more dynamic and flexible experience for certain kinds of fast-paced projects while still maintaining the benefits of more structure within the details.
Thanks for considering.
Fixed, can be seen in ‘ss’ popup on https://checkvist.com
-
Hi Aaron,
Thanks for the comment, but I'm afraid, this kind of behaviour is not easy to implement :( I hope to make it working at least for non-shallow mode, I've added this to the list of enhancements.
Best,
-
aaronrwilson commented
Hi KIR,
Thanks so much for implementing this. I just tested it and while it's nice as-is, there's one tweak that would make it work as I was originally hoping it would. That would be: When shallow sort is selected, any updates to a child task would count as an update to the top-level task (meaning to that task grouping since it represents a chunk of related work). That way the chunks of tasks would auto-sort (at the top level) based on which chunk had recent activity, without losing the intended structure of the child tasks. I think this is important because I rarely make edits directly to the parent tasks once it's turned into a parent container with many children tasks--the majority of the updates are happening at the child level.
Thanks again,
Aaron -
Hello Aaron,
Thanks a lot for your suggestion - it is quite reasonable. Currently we're trying to spend more time on the mobile version, but I hope we'll manage to squeeze in this sorting mode in the the Checkvist. At the first glance, it doesn't look like a complex one.
Thanks again,
KIR