Yes please. However, due dates really go hand-in-hand with reminders.

I would propose three types of task dates: Start Date, Action Date, and Due Date.

A controls when a task becomes available. Until this date arrives, the task is hidden from most views and treated as “not actionable yet.” This by ensuring you only see tasks that can actually be done now. This is useful for things like reminders for future tasks.

is for time blocking: to figure out when you’re actually going to work on the task. On the Action Date, the task should show up in your Daily Note. For some larger projects, this may need to be a range across multiple days.

A is a : a point in time when something must be completed or there will be a real-world consequence. The system should treat due dates as obligations, so tasks with them should show up as “Due Soon” or “Overdue,” creating urgency. Perhaps in the Daily Note page, in a new “forecast” section which provides a view of what’s coming next.

In essence, Start Dates govern visibility, Action Dates govern time planning, and Due Dates govern urgency. Used together, they create a clean workflow: you don’t see tasks before they’re relevant, you aren’t tricked into fake deadlines, and you still benefit from structure about when you will take action on certain types of work.

Thank you and congratulations to the Capacities team for your work on Task Management v1! It is a game changer to have integrated task management right inside Capacities.

I have chosen my current task management tool because my workflow is dependent on two dates: start (or schedule) date, when I want to work on the tasks, and a due date (or deadline), at which the task must be done.

We do have schedule date now - and without a due date, Capacities won't work for me.

In my opinion, on calendar, the due date should be visible as the coloured dot. Sorting and groupping by due date should be a possibility.

A Deadline or Due Date would be nice. It could influence the sorting sequence of tasks together with the priority.

I understand that the day in the Task object is actually the due date. Perhaps it should be labeled this way. Then having another date that we could use for the start date (also called in other systems Defer date or Planned date) could be used to start working on the task. Or perhaps it is the other way. If the team adds a new date it will have to be clarified.

Not all tasks have a due date (washing the car for example) but with a Planned date you can manage what you have to do on a specific day.

That’s how I manage my todos in my current system and that’s what it makes it really effective and usable, not being overwhelmed with too much tasks. I can only view the ones I actually have to work on.

We can set up views such as “due in the next 3 days”, “due this month” or “due this week” if there’s a due date property

Yes, in time management, it's helpful to track the date something is due separately from the date when I'm going to work on it. Those often coincide, but not always. Maybe:

Related: A feature I really like from Akiflow is the ability to set a week or month as a due date. Right now, making a task due "next week" or "next month" just sets the due date to the first day of the next week or the first of the next month. But a potentially more helpful bucket is to actually have a week or a month as the due date range, so when that week or month comes along, I can refine the due date to the specific day I want to do it. Just a thought.

If the task date was a date RANGE, most use cases would be covered I think.

In my opinion (others might disagree!) this would only be worth adding after task reminders get implemented...to have e.g. a reminder for the start date ("do date") and another reminder tied to the deadline ("due date").

The other thing for me would just be a simple "Deadlines" view tab that shows all open deadlines in one list.