This conversation actually bodes well for an improvement I've wanted which is to define my own statuses. We would be able to define which statuses represent Active tasks then and the project statuses could more closely mirror the statuses people have in real life.
For example IRL a project for us can be in many statuses* including Discovery, Feasibility (study), Design, Bid (out for), etc. One of these statuses is 'exploded' projects. These are projects that have ended but were not "completed" properly (ie. lost in bidding or otherwise, client/projects I've fired, been warned against or just decided otherwise to 'pass' on, the occasional/unfortunate less than stellar final outcome, etc.) I use these as a metric and when I do process reviews/writeups these jog my memory and remind of lessons learned. Presently I can't/don't denote these projects in MLO so I have to review my paper folders' system ( I keep the exploders sorted separately for that but it's messy (files in multiple sort orders/places)) So here is just one use case; it would be MUCH better for me to be able to review this in MLO than on paper. (and yes I probably could mock up some workaround or another based on flags or contexts but having project statuses conform to the way they are in the rest of my real-life systems are really the answer * For example our project bidding and design software uses these project statuses: Discovery, Feasibility (study), Design, Bid (out for), Negotiation/"Value Engineering", Awarded (Internal 'expansion' from Proposal to actual Project including assignment of production Project Number), Staging (JIT Purchasing), Bench/Pre-build (rack building), Rough-In (an In-Process construction state), Trim-Out (In-Proc constr state), Programming & Finish (In-Proc constr state), Commisioning, Training, In-warranty support, On-Boarding, Maintenance Plan support, Out of warranty, Blocked and Exploded. Tracking our sales pipeline would add a small handful more to that. These are all valid project states that we use for filtering projects and focusing on what needs to be done, delegated, tracked and/or pushed. On Monday, July 20, 2015 at 10:21:41 AM UTC-4, Dwight Arthur wrote: > > Am 20.07.2015 um 10:13 schrieb Christoph Zwerschke: > > This could be solved by adding another project state like "incubating" > > between "not started" and "in progress" which would be considered > > "active" as well. > > Yes, that would be an improvement. But there would have to be one more > called "shutdown" or "cleanup" just before completion. > > -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/a5fe8460-9d16-4839-a7be-93b8f7aa72d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
