Hi,

Thank you for your feedback!

You'd better put the tasks in Waiting which depends on when other tasks have been completed.

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

Thank you for your support!

Best regards,
Doit.im Team
—————————————
Facebook: http://www.facebook.com/imdoit
Twitter: https://twitter.com/doitim
Help Center: http://help.doit.im/
Blog: http://enblog.doit.im/
Group: http://help.doit.im/group/

@wendy_only and nameless

These tasks are not Waiting for either, because they are to be done by me personally, not by somebody else. I usually call them "subsequent tasks". In paper based GTD they belong in "project support" and you move them from "projects support" and onto your active Next and Waiting for lists when they become possible for somebody to do.

My suggestion earlier has been that there could be a "line" within each project - in the project view only - and only the tasks "above the line" will be visible on the active lists. All tasks below the line (the subsequent tasks) can be ordered manually into a more or less realistic sequence, but will be invisible on all other lists. The progression from below the line to above the line could be partly automated, to make sure always at least one task is above the line.

Currently I use a workaround for all this. I use Priority None for subsequent tasks. I split these subsequent tasks across both Next and Someday - the near future tasks (will soon be possible, only a few small things to complete first) I keep as No Priority Next and the more distant tasks as No Priority Someday. All my other tasks have a priority color, and No Priority therefore uniquely defines a subsequent task. When a currently active task is completed I change the priority of the subsequent now possible tasks from "No Priority Next" to "Medium Priority Next" (usually; or High or Low, but only if I have a special reason). This workaround It is not exactly pretty or "user-friendly", but it works well for me in practice.

@Folke
Hi,

Thank you for your feedback and sharing your tips with us.

We will reconsidering your suggestion seriously.

Thank you for your support!

Best regards,
Doit.im Team

+1

The outcome of a project planning is a list of actions to be done. These are not all next actions. Maybe you could implement a start or some similar concept to mark and distinguish a next action from a planned (but not next) action? Only the next actions would be visible on the widget lists. Also in Projects list only the next actions would be explicitly counted, so that I could know whether I have at least one next action established for every single active project (or maybe next/planned counter, for example: 1/3)

I've just realized that there is a star in the on-line version, but it means "Today" :-( Can't think of any other way it could be handled, maybe just another state for actions? Today, Next, Planned, Someday... It's something different than Someday or Waiting. I wouldn't actually want planned actions to show in any of those two categories.

@nameless

As for possible solutions, let us first look back at what GTD says.

In the GTD definitions, there is neither a Planned category nor a Today category (nor a Tomorrow category, for that matter). What you have is:

- Next actions, possible for me to do anytime (a.s.a.p) from right now and onwards (today, tomorrow, any day, any week ...)
- Waiting for actions, for somebody else to do, could be ready anytime from now onwards (today, tomorrow, any day, any week ...)
- Someday/Maybe, not sure if it will ever be appropriate, maybe never
- Tickler items, cannot be considered until a particular date at the earliest
- Calendar actions, agreed to be done (must be done) on a particular date (time)

The "planned" tasks (subsequent tasks; still "inactive" ) are also part of GTD, but not part of these "standard" well-defined lists or terms - there is no special word for them. They belong in the GTD category "project support" along with all kinds of other facts and documentation, the exact structure of which is undefined in GTD. But these "planned" tasks are definitely real, and they deserve proper treatment.

As I said, I am reasonably satisfied with my own workaround (described above), but I agree that a neat and clean solution would be nice. In my own opinion, implementing a Planned status as a category ("box") would be a workable way to do it, but perhaps not the best. It is not even nearly as bad as as having Today (or starred) as a separate box, but it is still wrong for the very same obvious reason. A real task can actually be "both" at the same time - e.g. both require your attention (star) and be someone else's responsibility (Waiting). This matters less with the "planned" subsequent tasks, though, because although in principle a task can be "planned" to be "waiting" or "planned" to be "next" (etc, in any combination), it is no super big deal if you have to recategorize the task when you it becomes active (i.e. you have to select Next or Waiting only at that late stage even if you have known all along what it will be). Also, once the task is no longer "inactive" it clearly does not belong among the "planned" tasks anymore.

The simpler and neater and also more logical solution would be if the task could be firmly categorized as Next (for me to do asap) or Waiting (for someone else to do asap) from the moment it is first entered and all the way until it is completed - totally unaffected by whether the task is temporarily inactivated (subsequent/"planned"/invisible) or active (visible on Next, Waiting or other GTD lists) or is starred for attention today (visible both on its GTD list and on the starred list).

@Folke I don't actually get the last part. Do you mean:
Stuff - > #Someday [Reference] OR
a) If someone else is expected to do something about it: #Waiting
b) My own asap: #Next
Plus:
Some kind of a new switch in the task form (Active/Inactive state).
Only active tasks visible on lists

Questions:
Where would you see inactive tasks? In projects? And if an inactive task was not a part of any Project?

Yes, you would see these inactive ("planned") tasks only in projects, because they depend on other tasks before them in the project.

Yes, the "switch" could be represented in the form of a horizontal line etc in the project, and you could make tasks active or inactive by dragging them across this line, placing them above or below. (But there could also be a checkbox in the task edit pane, as you imply.)

Yes, a Waiting task is for someone else to do. Often you know already at the planning stage that this task will be a Waiting task, so the ideal would be to be able to place these "planned Waiting" tasks sequentially in the same "inactive section/queue" as the "planned Next" tasks. (But if this is difficult to implement, then treating them as implicit Next would not be too difficult to work around.)

Sorry for expressing myself so foggily. (I could barely understand it myself)

+1

+1

@jacekrszewczyk
Hi,

Thank you for your feedback. Sorry that we have not take it into developing plan yet.