| | 1 | = Multiple Trac Coordinator = |
| | 2 | |
| | 3 | This is a proposal for Trac multiple project support by adding a layer above the current Trac implementation. |
| | 4 | |
| | 5 | Many people would like to use Trac in a multiple project environment but currently this isn't as great an experience as it ought to be. As [wiki:TracMultipleProjects/ByProductAndSearch this proposal] went down like a lead balloon (and I can understand why) this document sets out what would be required to coordinate multiple Trac instances, one per project. |
| | 6 | |
| | 7 | The following areas need to be covered: |
| | 8 | |
| | 9 | * Project index - a list of Trac instances by project name |
| | 10 | * Project summary page across selected projects showing: |
| | 11 | * Uncompleted milestones |
| | 12 | * Number of open tickets |
| | 13 | * Number of checkins (over a selectable period?) and who they were made by |
| | 14 | * Number of tickets closed (over a selectable period?) and who they were closed by |
| | 15 | * Tickets: |
| | 16 | * Ticket queries across a selected group of projects (e.g., all tickets assigned to me on all projects) |
| | 17 | * Milestone views of a number of selected projects on one page |
| | 18 | * Move (probably by copy/close) tickets from one project to another |
| | 19 | * Trac management: |
| | 20 | * Manage repositories, and trac instances (e.g. create, delete them) |
| | 21 | * Permissions across selected projects |
| | 22 | |
| | 23 | Many of these points are extraced from e-mails by solo turn and Robin Bowes after my last posting on the subjects of multiple projects. |
