Hi, Olivier. Group contexts already exist. Try this:
1. create a concept “group” (you probably want a better name). 2. Hit F8 (or select “Manage Contexts” from the MLO “Tools” menu) 3. Select “group” from the list of contexts in the left pane of the “Manage Contexts” popup 4. In the right pane, make sure the “included contexts” tab is selected and check off the contexts that should be included in Group. 5. Hit “close” Group contexts can have their own tasks or can just contain other contexts. Examples: my @computer context contains no tasks, just other contexts (+laptop, +phone, +web). My @home context has something over 100 active tasks right now and also contains two other contexts, +yard and +basement. You can make multiple layers – one of the contexts included in “group” can itself be a group and contain other contexts. I’m confused by your phrase “inactive project” – Like any item, projects have an activity status which can be active or inactive depending on dates, dependencies, uncompleted children or siblings, time of day in relation to open/closed hours of the assigned context, and other factors even more obscure. But it does not sound like this is what you are talking about. I think you mean project-not-started status. Are you supporting the request for some automated process that changes project-not-active status and/or the activity status of tasks within the project in order to promote better alignment between the two? I am philosophically in favor of such a thing but I share Lisa’s concern that it would need to be thought through very carefully. Many people use MLO in different ways and a small, obviously-beneficial change often has the effect of making big problems for a group of users who are doing something you never thought of. For example, when I tried to come up with a rule that would work, I thought of this: If any task within a project or the project itself has reached start date while project status remains not-started then change project status to In-progress. But then I realized that this would destroy a view I use that shows projects that should have started but didn’t. Then, I thought about saying that when any task within a not-started project is completed, change the project status to in-progress. Then I remembered recently when I was buying materials for a project I was starting and I also picked up materials for a project that was coming up. I went into the future project and marked the “buy materials” task completed. But the project was definitely not started, and should not start yet. It would have been a definite distraction for the future project to be showing up on my “today’s work” view. If you think this should be done, why don’t you try your hand at writing a rule that says “if [condition] (…and/or/not [condition]) then change [indicator] to [value]) and post it here. Forum members will be able to see if it would work for them and maybe we will get somewhere. -Dwight From: [email protected] [mailto:[email protected]] On Behalf Of robisme (Olivier R) Sent: Friday, January 04, 2013 7:32 AM To: [email protected] Subject: Re: [MLO] Re: Feature Request: Add/Edit entries in "Project Status" field I've just discovered today that a taks belonging to an inactive project is not automatically considered as inactive. This should be the normal behavior, shouldn't it ? To add to Mok idea, that I find good: I also have a lot of context and it is a mess now. I think that a kind of categorisation/organisation of contexts would be good. Two possibilities came in my mind: 1: to add a second context field 2: to be able to group contexts (as an outline of contexts) Le mercredi 2 janvier 2013 18:59:17 UTC+1, Lisa S a écrit : I would be concerned with the idea of automating changes based on project status. The concept of "Active action" is already complicated enough for new users. I'm not saying I am completely opposed, but it needs to be very well thought out to make it usable. On Wed, Jan 2, 2013 at 5:53 AM, Dwight Arthur <[email protected] <javascript:> > wrote: Hi, Mok. There are two frequently requested features related to project status. The first is for an additional value for the status field, and you suggestion shows an excellent way to meet that request. The second it for some workflow automation between the Project Status field and the task status, for example, that all tasks in a Not Started project would be inactive tasks. Would your solution to the first request make it more difficult to implement the second? Would we have to chose which request we liked better and abandon the other? -Dwight On Wednesday, November 10, 2010 5:17:56 AM UTC-5, MOK | MATSURU wrote: ... My wish is to have the ability to alter and add in additional entries to the [Project Status] field, which is similar to the "Context" field where we can enter/delete the entries freely. ... -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To view this discussion on the web visit https://groups.google.com/d/msg/mylifeorganized/-/DHnP2mOq_1MJ. To post to this group, send email to [email protected] <javascript:> . To unsubscribe from this group, send email to [email protected] <javascript:> . For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en. -- Lisa _____ Lisa Stroyan, mailto: [email protected] <javascript:> -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To view this discussion on the web visit https://groups.google.com/d/msg/mylifeorganized/-/_VYJacXdsisJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en. -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en.
