area vs projects
Hi there,
When I move a task to a project, it seems the "area" is removed or disappears. Is this a bug?
3 people watching.
-
New Issue
-
Conversation Started
You've started a conversation with the Nirvana staff to resolve this discussion.
-
Close the discussion Close the discussion
Private Permissions
This discussion is private. Only you and Nirvana support staff can see and reply to it.
Recent Discussions
| 07 Mar, 2012 04:47 PM | iPhone, Android & iPads oh my! | |
| 08 Dec, 2011 10:32 PM | Graphical markers | |
| 01 Apr, 2012 11:26 PM | significance and source of task id | |
| 07 May, 2012 05:17 PM | Diablo III Review | |
| 07 Oct, 2011 02:00 AM | Options for GUI color scheme |
2 Posted by Lasse on 26 Apr, 2011 07:29 AM
@Chris,
when you move a task to a project, it adopts the project's area. This behavior is intended because in GTD projects aren't a collection of various independent tasks that belong to a common category (say "finances", for example). Instead, a project is an outcome ("paint living room") that takes more than one step to achieve ("decide on color", "buy paint", "paint living room"). That's why sub-tasks (tasks within a project) always belong to the same area as the project.
3 Posted by Proximo on 26 Apr, 2011 06:37 PM
Perfectly explained by Lasse. :-)
4 Posted by Chris Lee on 26 Apr, 2011 06:48 PM
ignore