> I'm planning on mocking up some UI changes to reflect the proposed > changes I've brought up, but I haven't gotten to that yet. Briefly, I > find the number of boxes on the project page to be somewhat > distracting, > so I'd like to consolidate all of the existing information into a > single > box, and use lists to display the different information, adding to that > a list of child projects within the project, if any. Actions for a > project include only immediate child actions, not all descendant > actions > (though each child project should be listed with a count of its own > actions.) At the top of the project page, I'd remove the navigation > link > for next and previous actions, replacing it with a breadcrumb that > traces back to the top-level project.
I'm not sure I like these ideas, but I'll wait for the mock-ups :-) > Regarding task dependencies, I realize that may have different > meanings to different people, so here's the user scenario I had in mind > when I brought it up: sometimes a task or project stalls until another > task or project is complete, so the idea is that you can link those > tasks so that when the independent project/task is completed, the > dependent task becomes a next-action automatically, or moves from a > deferred to an active state. This would be really useful with > multi-user interaction, where i can delegate a specific task to another > user in the system, and when that user marks it as done my task is > automatically flagged as active. Obviously multi-user capability > isn't > there yet, and the dependency feature will require a model and UI for > notifications and/or watching other tasks and projects. > AFAIK, this is exactly what Eric is working on Reinier _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
