Overdue tasks can be assigned to members

[nickeltea]

As can be seen above, a task due in 2002 can be assigned to a member of the team. This behaviour is not specified in the user guide.

Since the functionality does not work as expected, this is a functionality flaw.

[soc-se-bot]

Team's Response

Thanks for raising this. However, this was an intentional decision - in particular, we believe it would be more confusing if overdue tasks cannot be assigned. We can see a few use cases for this

1. For bookkeeping purposes - a user might want to update task info (including assignee and whether it is done) after it is overdue, even if it was done in the past
2. Just because a task was overdue doesn't mean it doesn't need to still be completed

Finally, this behaviour is similar to every todo list application we have looked at, including Todoist, Notion, Asana, etc., hence we do not believe it is unexpected behaviour. As such, we do not think this is a bug.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

:question: Issue type

Team chose [type.DocumentationBug] Originally [type.FunctionalityBug]

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---