Is anyone actively working on functionality to cover subprojects or multi-user interaction along the lines of delegation and watching someone else's actions/projects? These are high-priority items for me, and if no one else is working on them, I'd like to take a crack at it, or work with someone to avoid duplication of effort. I've seen tickets in Trac for these functions, but they don't seem to be updated recently (there's also multiple tickets covering each, so i may be missing the active ticket).
Here are my implementation thoughts: 1) subprojects: this can be really simple. All that really needs to be done is add a 'parent' field to the project model and make some UI updates. Projects with null parents correspond to top-level projects, which can be thought of as areas of responsibility. subprojects have another projectid assigned to them for a parent. hiding a project cascades down the tree, marking it visible flows up the tree. One of the tickets mentions sub-actions, which i think is kind of a corruption of the metaphor--actions should by definition be discrete pieces of work or steps to be taken, not aggregations of them. this would also make it really easy to implement conversion of an action to a project, setting the parent id to the original action's project, which is also something I'd really like to see, though its far lower on my priority list. 2) multi-user functions first i'd like to implement 'watches', which would allow one user to view the projects, actions, and notes of another user. further down the line it could be used to implement notifications and dependencies. The watch UI would allow a watching user to copy a project definition to his own list of projects, and optionally its child actions/projects. second step in this would be to allow a user to delegate an action or project to another user. To do so, it would seem like all you would need to do is reassign the user_id. As a first go-round it would fit my purposes merely to allow any user to delegate to any other, but it could be implemented in such a way as to allow a delegation to follow a request/accept model. So now that I've laid out what I'd like to work on, does anyone have any thoughts about it? Is anyone else working on this or similar functionality, or in a different direction? Best regards, Keith
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
