What is the use of contexts for projects? | Help Center

What is the use of contexts for projects?

PRO

fladd 03/23/2014 20:29

Platform:All

Can anyone please explain to me what the use of contexts is for projects?

I can assign a context to a project, but this has absolutely no effect at all. The project will not show up when I click on context, and also with an advanced search I can only filter for tasks.
Also, since there is no context inheritance, the tasks assigned to a project are not affected by the project context. So again, the project context does not do anything it seems.

So what exactly is the practical use of assigning a context to a project?

wendy_only post on 03/24/2014 08:08#1

PRO

@fladd
Hi,

We are considering this issue now. We have the plan to improve this feature.

If you have detailed suggestions,please tell us. Thank you.

Best regards,
Doit.im Team
Folke post on 03/24/2014 08:39#2

PRO

This is a quite typical weakness of Doit. It is only half-finished. You can define lots of things, but then you cannot really do anything with it, and often you cannot even see it:

Contexts: Yes, they can be defined even for a project, but they are not inherited to the tasks, and the projects names themselves typically do not show up (in the Context lists etc), so you really have no use for them at the project level. (And besides, contexts in the GTD sense do not make much sense to a project, anyway.)

Tags: Yes, they can be defined, but only for tasks. They are neither definable nor inheritable from projects or goals, and you cannot even see them in the list. Not much use at all, but has huge potential.

Goals: Yes, you can organize projects under goals, but then you cannot really see this anywhere in your lists or use it for grouping or filtering or anything. Highly limited use, but hast huge potential.

Repeat: Yes, you can define repeat patterns for tasks, but you cannot see in your list when the next occurrence (or next deadline) is. Like being totally blindfolded.

I think Doit and its users would benefit more if Doit were to finish all such basic existing features rather than keep introducing all kinds of new dubious features.
fladd post on 03/24/2014 19:31#3

PRO

Mmh, I see...
I was actually considering paying for the Pro version once my first month of free usage goes by, but I am not sure if I want to pay for a half-finished product...
wendy_only post on 03/25/2014 07:10#4

PRO

@fladd
Hi,

I want to say that it is not a half-finished product as we need improve the project all the time with users' new requests and that we find better ways. There is no best,but we will make it better and better.
fladd post on 03/25/2014 15:29#5

PRO

Sorry, I was a bit unclear here. What I meant to say is that there are some features in the product which are half-finished (or actually, in case of the contexts for projects, features that have no use).
wendy_only post on 03/26/2014 07:37#6

PRO

@fladd
Hi,

That's all right. We will make Doit.im better. Thank you.
faberv post on 03/18/2015 19:21#7

PRO

Hello,
it would be really nice, if when I assign context for project, so this context would be also assigned for every tasks in this project automaticly. It is anoying to assign each new tasks in same project to same context..

Otherwise Doit.im is really powerfull GTD system and I'm considering to pay it.
wendy_only post on 03/19/2015 03:03#8

PRO

@faberv
Hi,

Thank you for your feedback.

We are considering add this feature now.

Thank you for your support. We will work harder.

Best regards,
Doit.im Team