A user's assigned tasks will now return based on the task's due date, from earliest to latest.
Also allows the future tasks not to be given to the user on the tasks page.
Related JIRA tickets:
INBA-929.
INBA-853.
How should this be manually tested?
Assign a user several tasks. They can be different projects or the same one, preferably with the individual tasks have different end dates. Log in as that user and confirm that the due dates are ordered. (See screenshot below.)
Also, give a user a task in the future. It should not appear in the list. Change the start date for that particular task in the back end (under the Tasks table) and it should then appear when the user refreshs.
Background/Context
Tasks are given an initial end date based on the stage's end date. The task's end date can be changed if the admin goes into the tasks and chooses a new date from the "Task End Date" up top.
What does this PR do?
A user's assigned tasks will now return based on the task's due date, from earliest to latest.
Also allows the future tasks not to be given to the user on the tasks page.
Related JIRA tickets:
INBA-929. INBA-853.
How should this be manually tested?
Assign a user several tasks. They can be different projects or the same one, preferably with the individual tasks have different end dates. Log in as that user and confirm that the due dates are ordered. (See screenshot below.)
Also, give a user a task in the future. It should not appear in the list. Change the start date for that particular task in the back end (under the
Taskstable) and it should then appear when the user refreshs.Background/Context
Tasks are given an initial end date based on the stage's end date. The task's end date can be changed if the admin goes into the tasks and chooses a new date from the "Task End Date" up top.
Screenshots (if appropriate):