Some thoughts: 1) Given that we can always change the state of the project between active, completed and hidden, I think the best would be to mark it 'completed' and then change it back to active if required. You can always write yourself an explanation 'note' if the project is not really completed but dead/canceled...
2) I agree. 3) Separation by state would be a good idea. So all completed projects would be listed separate from all active projects etc. 4) It does make sense but I do not really agree with the alphabetic listing. I would rather have an ordering based on the number of actions associated with the project. The same goes for 'context' too. I am sure someone else will prefer a different order :) 5) Isn't it enough to reuse the older project by changing its status from completed back to active? 6) Support both the need for link as well as the need to limit it to active projects and contexts SK ---------------------------------------------------------------------- Date: Sun, 25 Feb 2007 19:40:00 -0500 From: Luke Melia <[EMAIL PROTECTED]> Subject: [Tracks-discuss] Interacting with Projects in Tracks To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Hi Tracks fans, I was doing a review of my projects in Tracks (using the trunk version) and found myself dissatisfied with the experience. A few thoughts: 1) Some projects have no remaining next actions, and there is nothing more to do, but I didn't complete them. They're no longer applicable for one reason or another. Do I mark it Completed? Hidden? Do I delete it? Or is there a new state necessary - "dead" or "canceled"? 2) It seems to me that only "Active" projects should appear in the Autocomplete box in the new action form. Any objections? 3) On the project listing page, my list is getting too long to be useful. Perhaps we need to divide it into separate lists, by state? 4) Does ordering projects make sense? I find myself just trying to keep projects listed roughly alphabetically (but am never up to date). Do you use that feature? 5) Because we use the project name to create a URL, you can't create a project with the same name as a previously completed one. This is problematic for certain projects. For example, I have a project "Upgrade my blogging software", which I already completed but now need to do again. 6) Ticket #379 [1] on the Trac suggests next/previous links when viewing individual projects and contexts. I like this idea a lot, but I think I only want it to include Active projects or contexts. Looking forward to your thoughts on these topics or other related to managing and interacting with projects in Tracks. Cheers, Luke [1] http://dev.rousette.org.uk/ticket/379 __________________________________________________________ Yahoo! India Answers: Share what you know. Learn something new http://in.answers.yahoo.com/ _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
