Home page view shows tasks with start dates that have yet to pass. #2028

Closed
opened 2023-03-22 17:40:30 +00:00 by james7132 · 8 comments

Description

  1. Create a new task.
  2. Set the start date to some time in the future (I used 10/01/2023)
  3. Task shows up in "Current Tasks" on the root page.

I'd expect that tasks that don't start for another 30.

Client: Desktop client, Windows v0.20.3
API server: v0.20.4

Vikunja Frontend Version

v0.20.3

Vikunja API Version

v0.20.4

Browser and version

Desktop App

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

image
image

### Description 1. Create a new task. 2. Set the start date to some time in the future (I used `10/01/2023`) 3. Task shows up in "Current Tasks" on the root page. I'd expect that tasks that don't start for another 30. Client: Desktop client, Windows v0.20.3 API server: v0.20.4 ### Vikunja Frontend Version v0.20.3 ### Vikunja API Version v0.20.4 ### Browser and version Desktop App ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots ![image](/attachments/a8643c90-3a8d-4cb1-b26c-91db737b2d6b) ![image](/attachments/0683c78b-a475-4716-aa7b-6f1c103aa446)
james7132 added the
kind/bug
label 2023-03-22 17:40:30 +00:00
Member

I think we don't have a clear definition what 'current' means in this context. I assume you are under the (legitimate) impression that it means tasks of the current day. I think (didn't check) currently it's just a list of the tasks in the order they were created.

I think we don't have a clear definition what 'current' means in this context. I assume you are under the (legitimate) impression that it means tasks of the current day. I think (didn't check) currently it's just a list of the tasks in the order they were created.
Author

As a user here, I fully expect that the list of "Current Tasks" are tasks that are currently within scope. What's the point of doing a task that cannot be started yet?

As a user here, I fully expect that the list of "Current Tasks" are tasks that are currently within scope. What's the point of doing a task that cannot be started yet?
Member

Of course. I get your argument and I think it's valid

What I mean is that the title doesn't say "today" but "Current tasks". So it makes sense to me to show a small preview of the future. In the evening for example I might want to look at the tasks of tomorrow. If we don't want that and these should really just be tasks of the current day the title should be adjusted accordingly.

It seems right now we show tasks in the order they were created or something similar (didn't check).

Of course. I get your argument and I think it's valid What I mean is that the title doesn't say "today" but "Current tasks". So it makes sense to me to show a small preview of the future. In the evening for example I might want to look at the tasks of tomorrow. If we don't want that and these should really just be tasks of the current day the title should be adjusted accordingly. It seems right now we show tasks in the order they were created or something similar (didn't check).
Author

Probably should be separate feature request issue, but having controllable list views with differing sort orders and filters (urgency, priority, due date, etc.) would be great. I heavily leveraged this during the brief time I was using Todoist.

Probably should be separate feature request issue, but having controllable list views with differing sort orders and filters (urgency, priority, due date, etc.) would be great. I heavily leveraged this during the brief time I was using Todoist.
Owner

The home page only filters by due dates, showing you the tasks with a closest due date first and then the others. After that it shows the tasks by creation date, that's why it showed the task in your example with the start date some time later. If you'd have another task with a due date it would show that before the other one.

I agree the wording could be better but to me, this works as intended. Different users have different needs for what is "current" so we try to provide a base line here and every customisation of that should happen via saved filters. I think there's an item somewhere in the backlog to let the user select a saved filter to be shown instead of what "current" is right now.

Probably should be separate feature request issue, but having controllable list views with differing sort orders and filters (urgency, priority, due date, etc.) would be great.

Did you check if saved filters do that for you?

The home page only filters by due dates, showing you the tasks with a closest due date first and then the others. After that it shows the tasks by creation date, that's why it showed the task in your example with the start date some time later. If you'd have another task with a due date it would show that before the other one. I agree the wording could be better but to me, this works as intended. Different users have different needs for what is "current" so we try to provide a base line here and every customisation of that should happen via saved filters. I think there's an item somewhere in the backlog to let the user select a saved filter to be shown instead of what "current" is right now. > Probably should be separate feature request issue, but having controllable list views with differing sort orders and filters (urgency, priority, due date, etc.) would be great. Did you check if saved filters do that for you?
Author

I agree the wording could be better but to me, this works as intended.

I will note that this causes repeating tasks to seem like they're immediately returned to the docket to be done again. Something I'd consider horrible UX on the default view for a user.

It'd be ideal if I could pin some of these filters to the home page instead of the default unfiltered view to allow the user to customize what they prioritize.

Did you check if saved filters do that for you?

They can deliver filtered views, but lacks the sorting that I'd like.

> I agree the wording could be better but to me, this works as intended. I will note that this causes repeating tasks to seem like they're immediately returned to the docket to be done again. Something I'd consider horrible UX on the default view for a user. It'd be ideal if I could pin some of these filters to the home page instead of the default unfiltered view to allow the user to customize what they prioritize. > Did you check if saved filters do that for you? They can deliver filtered views, but lacks the sorting that I'd like.
Owner

I will note that this causes repeating tasks to seem like they're immediately returned to the docket to be done again. Something I'd consider horrible UX on the default view for a user.

This is being discussed here: https://community.vikunja.io/t/repeatable-tasks-appear-to-just-have-start-due-dates-reset-instead-of-creating-a-clone/468/2

> I will note that this causes repeating tasks to seem like they're immediately returned to the docket to be done again. Something I'd consider horrible UX on the default view for a user. This is being discussed here: https://community.vikunja.io/t/repeatable-tasks-appear-to-just-have-start-due-dates-reset-instead-of-creating-a-clone/468/2
Member

[...] filters by due dates, showing you the tasks with a closest due date first and then the others. After that it shows the tasks by creation date [...]

Maybe we can make it clearer what is shown in the meantime by adding this info in a info popup next to the headline.

> [...] filters by due dates, showing you the tasks with a closest due date first and then the others. After that it shows the tasks by creation date [...] Maybe we can make it clearer what is shown in the meantime by adding this info in a info popup next to the headline.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#2028
No description provided.