Moving completed tasks to the end of the list #2426
Replies: 9 comments 11 replies
-
|
Hi, I'm very happy to have this discussion. Just not in tl;dr I'm going to move it to a Development Discussion. As per the title of this section - (Bugs have always been tracked in Issues.) Here are some of the reasons why the need for this change: I had to leave Ideas Discussions open to allow people to comment on existing ideas, and so we could track their votes, so I renamed the section to try to point people to Ideas instead for new reports. |
Beta Was this translation helpful? Give feedback.
-
|
Ah ok, I thought feature requests still needed discussion first before moving them to issues. |
Beta Was this translation helpful? Give feedback.
-
Yes, that was the original intention, before I took over Tasks... the linked issue above tries to describe the difficulties and limitations with that... |
Beta Was this translation helpful? Give feedback.
-
Yes, the reason for that conclusion so far is that I expect that moving tasks around will demand a lot of configuration and a lot of testing. And the backlog for Tasks is already overwhelmingly large - and large new things that are already done by other plugins is just not good for (my) morale.
It would be very helpful to have alternatives documented - if anyone has time to try them out, I would love to see brief write-ups in this section of the docs: https://publish.obsidian.md/tasks/Other+Plugins/About+Other+Plugins |
Beta Was this translation helpful? Give feedback.
-
|
In case it helps finding related topics, here are links to the more or less related issues and discussions...
|
Beta Was this translation helpful? Give feedback.
-
|
I've tweaked the table above to include the descriptions of the labels |
Beta Was this translation helpful? Give feedback.
-
|
The plugins mentioned so far, here or in Discord, are:
And for hiding completed tasks: |
Beta Was this translation helpful? Give feedback.
-
|
I've asked in Discord in case I missed anything out. |
Beta Was this translation helpful? Give feedback.
-
|
@Cito Having looked at Task Archiver and Task Collector, I am even more confident in my decision to not replicate that work in Tasks. They are rich in features. If you were inclined to try them out, and contribute documentation to share the information above, it would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
I have now tried out everything, here is my summary:
Unfortunately, though particularly Archiver looks quite useful, none of them does the simple thing I have in mind: immediately on checking a task off, move it to the bottom of the same list. At least I could not figure out how to do it with any of these plugins. I'm thinking about implementing it myself. What would you prefer: Releasing it as a separate plugin or submitting a PR to Tasks? |
Beta Was this translation helpful? Give feedback.
-
|
Wow, thank you very much indeed for the write-up!
Interesting... I had not considered your contributing it as an option... Two things make me think it's worthwhile putting it in Tasks (big U-turn!):
Things you might like to consider:
I've tried several times to unify that code, removing repetition - and not yet succeeded... If you are not scared off by that complexity, then yes I'd love to have you contribute the feature that you need. Thank you. ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
Have you thought about how it might work with nested list items, either where the completed is indented, or itself has indented items? The only think I can think of is to say that if there is any indentation it won’t move the completed task, for safety… |
Beta Was this translation helpful? Give feedback.
-
|
Different status flags should not be too difficult to handle. I would just take those that are considered to mean "completed" (probably configurable), and move only those. Regarding nested list (i.e. nested tasks), I would move only at the current level of the list. If the task has subtasks, I would move it together with its subtasks. Maybe there should be also a way to specify that certain notes should be exempted from the auto-move behavior, in addition to a global option (e.g. using a flag or a note path). So it's on my personal to do list now. Not sure if and when I will be able to work on this though, and there are already one or two other Tasks features on the list... |
Beta Was this translation helpful? Give feedback.
-
Indeed. If implemented in Tasks, that would be obtained via
That sounds great. I was also wondering about when the nesting involves non-tasks... Here's a mashed up sample: Nested tasks and non-tasks example.md
Yes, I have been thinking for some time about defining some frontmatter properties to override Tasks settings on individual notes, and this would be a good example for that.
Understood. Thinking about the above, realistically this is going to be a lot of work to work in to the Tasks code, just because of the current data storage in Tasks. I do wonder if the most effective way of doing it might be to implement it in a separate plugin first, and define the data structures that work well for it. And then that code could be migrated in to the Tasks incrementally. Having data-storage in Tasks that knows about adjacent text would open up many opportunities for implement some very popular user requests. |
Beta Was this translation helpful? Give feedback.
-
|
Hello! I have the same feature request and after searching, I found this topic! I believe that the task reorder feature in Apple Reminders could serve as a useful reference: 9bf4250e442705766a23760ea6d72882.mp4Furthermore, although there are currently many plugins available to accomplish this task, I am curious if there is one that can directly trigger the "Re-order" function after completing a task. Additionally, could the new |
Beta Was this translation helpful? Give feedback.
-
|
Moved to the Ideas section, as once the work on storing sub-tasks is implemented, this will become feasible. No idea when it would be implemented though. |
Beta Was this translation helpful? Give feedback.
-
|
I've updated the docs to mention this request: e26eba2 |
Beta Was this translation helpful? Give feedback.
-
|
and published here: |
Beta Was this translation helpful? Give feedback.
-
|
I’ve made a plugin that sorts tasks automatically; it might be useful until this is supported by Tasks itself. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. To save others from having to spot it on that Obsidian link, here is its GitHub link, to get more info directly: |
Beta Was this translation helpful? Give feedback.
-
When I have a task list that I process directly (not via a view), it would be helpful if tasks that have been marked as completed could be automatically moved to the bottom of the same list, so that the next actions always appear at the top of the list. It could be made configurable whether completed tasks should be moved to the very bottom of the list or right before the first completed task in the list, which would order the completed tasks either in ascending or descending completion order.
Some ideas going into a similar direction have already been proposed (see #139, #212, #493, #2318).
It looks like the decision so far was to not let this plugin move tasks around, and let this be handled by other plugins (and more generally for all checklists). I still created this idea to document our decision and possible alternative solutions (plugins that can be used for the purpose), and as an opportunity to reconsider the past decision about moving tasks, since it seems to be such a common request.
Beta Was this translation helpful? Give feedback.
All reactions