-
-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow customisation of groups in group by due
, e.g. "this week", "next month", "future"
#1876
Comments
Thank you for the suggestion. Could you please explicitly spell out what the results of this should look like, and how you feel that Tasks would be able to parse generic text like this:
I have done the following sort of thing, and found it quite effective when I use
|
Also, what do you think Tasks should do if there are any tasks that match the query and which do not fall in to any of the headings given by the user? For example, given your query, tasks which are due before today, or have no due date... |
Thanks Clare, let me try answer:
I'd expect something similar to:
Here you'll see that there is no "Tomorrow" heading as there are no tasks due tomorrow.
I have done this in the past but it gets annoying because I have the headings. I think that this is what I'm trying to avoid. |
I think the current behaviour of "No due date" with |
Aahhh - so I think there may be something missing from your spec then. I originally thought the request was:
But now it seems to be:
What if someone said:
Which would look like it is a very valid thing, when looking at the proposed feature above... And what would the default group name be then? I understand what you are requesting, but I am concerned that that it is a rather specific proposal for a rather specific problem... And there will be other requests for similar but subtly different things... Other optionsThere is in in-progress Pull Request that would allow users to write functions to define their own groups. I do feel that this would be a more appropriate solution to what you are proposing. Another alternative is this feature request: Which would be a lot easier to implement, test and document than the proposal here - and could probably be generalised to grouping my month, quarter or year... |
I've thought about this and decided not to implement it. The features listed in 'Other options' above will be both easier to implement and more generally useful. The first - Group by functions is coming fairly soon - and will give a lot of flexibility. |
🔖 Feature description
When using
group by due
I get a sub-heading for each day, some days have a single task which means a lot of space is wasted. Additionally it is difficult to see at a glance if "YYYY-MM-DD Friday" is this Friday, last Friday or some other future Friday.I'm looking for a way to further customise the size of the groups.
✔️ Solution
I might ideally write:
❓ Alternatives
Many
tasks
queries, one for each group/bucket I'm interested in, where I implement my own heading. This has the downside of showing up "This week\n\n0 tasks\n\nNext week\n\n0 tasks\n\nFuture\n\n[huge list of tasks]".📝 Additional Context
No response
The text was updated successfully, but these errors were encountered: