Correction:
..... orphan TASKS created during a project's inactive period
Adding task to inactive project cause inconsistent behavior
Steps to reproduce:
Create a task using quick add, and use "#....." smart tag to bind to an existing project that's inactive.
Expected result:
The task should be categorized as "someday", as is with the project and all other tasks within that project.
Actual result:
The task is categorized as "NEXT".
Also it is now impossible to move this task to someday even if you turned the project back to active and again turn to inactive. Basically the project active / inactive now can't affect these orphan projects created during a project's inactive period.
Create a task using quick add, and use "#....." smart tag to bind to an existing project that's inactive.
Expected result:
The task should be categorized as "someday", as is with the project and all other tasks within that project.
Actual result:
The task is categorized as "NEXT".
Also it is now impossible to move this task to someday even if you turned the project back to active and again turn to inactive. Basically the project active / inactive now can't affect these orphan projects created during a project's inactive period.
-
04/06/2014 17:58#1PRO
-
04/08/2014 10:41#2PRO
@zmfile01
Hi,
Now task with project will be automatically added to Next if you do not set start time. Do you want the task to go to Someday if the project is inactive?
Best regards,
Doit.im Team -
04/09/2014 15:55#3PRO
Yes. I think that would make more sense.
Otherwise, having tasks under NEXT when the whole project is SOMEDAY is at least confusing. It will make project - task association inconsistent. -
04/10/2014 03:01#4PRO
@zmfile01
Hi,
Now when you inactive a project, we will not move the Next tasks to Someday. We will consider your suggestion seriously.