@thewallfishgtd

Hello,

It is not a bug, but a current rule in Doit.im. Tasks under an inactive project will be shown nowhere except in the project and when the inactive project tuns into an active project, tasks under will be shown up in their corresponding box. For example, tasks starting tomorrow will be shown up in Tomorrow box. Because for active projects, what you need to focus on is the tasks under it.

And in your opinion, where should the tasks with no projects but not being activated (in Someday box) appear?

Thanks for your support on Doit.im.

Hi,
thanks for your quick feedback !

If I had to design the specifications, I would define the following for tasks and projects:

- if INACTIVE (someday), only show them in focus = someday and in its goal, if a goal is set. And for the projects, also in projects, but hidden as you are doing now: not in the left pane, but in the project list, in the someday section. So, NOT in any context, since the contexts items are intended to show what is doable in a given context. If something is inactive, it should not clutter the list of doable tasks

- if ACTIVE: same, + show them in context too.

That's what my design would be.

But what I meant was DIFFERENT: I am fine with your design, and it is OK to show something inactive in the Contexts menu. But then it should be consistent: both inactive tasks AND inactive projecs should be displayed there, or none of them. But displaying inactive tasks and NOT tasks of inactive projects is very misleading, since by essence, a project is a task (in the GTD philosophy).

Best,
Eric

@thewallfishgtd

We will seriously consider your idea on the display of tasks and projects.

And here, you said, "But displaying inactive tasks and NOT tasks of inactive projects is very misleading, since by essence, a project is a task (in the GTD philosophy)". Here comes our explanation: a project in Doit.im is also a task, but with multiple steps. So inactive projects are shown under the context you assign to them. Then since the inactive projects have been shown under the context, there is no need to show the tasks under them.

Shall you need any other help or have additional questions, please do not hesitate to contact us.

Thank you for your feedback and support.

Hi,
thanks again for the very quick answer.

Allow me to disagree with something you said: "Then since the inactive projects have been shown under the context, there is no need to show the tasks under them".

The project has a context, and its tasks might have a *different* context.

Practical example: project context = home, project date = someday, most tasks have context=home, but one task has context="with Mr Smith". I rarely go to Mr Smith's, so when I am there, I check the context "At Mr Smith", to see all the things I have to do there. My task won't appear in this context, since tasks of inactive projects don't appear in the context menu in the current implementation. So:

- either we say that the project is inactive, so I should not focus on its tasks, and thus it is a good thing that the task doesnt appear in context "At Mr Smith", in order to decrease the clutter. But then, for consistency, the inactive project should not appear in context = "home", to decrease the clutter too.

- ether we say that the task should appear in its context menu ("At Mr Smith") whether its project is active or not. This could make sense because someone that has nothing else to do at mr smith's place can start a task of an inactive project, in order to optimize his time, and he could know what to do only if the task --of the inactive project-- appears in its proper context. in this case, if we are consistent, the that task should appear in "Mr smith" context, and the project in "home" context.

I find these two behaviors consistent. But the current one, which is a mix of the two, doesn't seem consistent to me.

AFAIK I like option two above much better : one can group items (tasks / projects) by start time, and inactive tasks will be grouped at the end in the "someday" category : 100% information, 0% clutter.

Cheers
Eric

@thewallfishgtd

We will seriously consider your thought above.

If there is anything else that we can help with, please feel free to contact us.

Thanks for your great support.

I would suggest to introduce an "inactive status" at task level - For that matters create a bucket and call it Inactive similar to Someday, to have somewhere to store the inactive tasks. The reason:

On Active projects, I often have perhaps 5 tasks defined, but in most cases ONLY ONE of them is THE next action to take. I define the next action for each project during my reviews of the project lists (This is pure GTD practice) and I don't want all those other actions to show up anywhere. When I have completed the next action for a project ideally the project should have a visula ndicator that it has no next action defined, or more advanced perhaps a feature to automatically change the status of the next taks in sequence from Inactive to Next action. You should take a look at how this is implemnted in Thinking Rock. That is the cleanest and most GTD pure tool I have ever used, however it is buggy, the interface inefficent and not cross platform

@NEODK

Thank you for your info.

We just have it in our development and believe it will be implemented soon. Please be patient.

Shall you need any other help or have additional questions, please feel free to contact us.