| 149 | | The top-level project should also be able to present a ''Projects'' main navigation entries, showing a list of the available projects, much similar to the list of Milestones. |
| | 147 | There should a standard way to change the current list of active projects: typically that would be a pull-down menu as described in [#Focalproject] above, somewhere near the top-left corner, for Mantis refugees. Next to this simple selector should be a (+) link to open a more advanced project selector ([#ProjectTree]) showing the projects "pre-selected" by the choice of the focal project, but in which additional projects could be opted in or others could be deselected. |
| | 148 | |
| | 149 | For example, there should be a ''Projects'' main navigation entry, which corresponds to a page showing some details about the currently selected projects and pointing to the parent and children objects if they're not themselves selected. This would be much similar to the list of Milestones, and likewise selecting a project would go to that project summary page (#1). |
| 153 | | Existing modules that lend themselves to cover multiple projects should be adapted and provide a standard way to specify multiple projects when accessed from the toplevel project. This can take the form of a list of checkboxes, a multiple selection field, or a text field for entering a pattern. |
| 154 | | When those modules are accessed within a dedicated project (parameter 'project'), they should behave similarly to the single project Trac, i.e. not offer the possibility to cover different projects. But when the project is the top-level one (`project == ''`) or there are already multiple projects specified, then the possibility to select different projects should be offered. |
| | 153 | Existing modules should progressively be made project aware and will filter their content according to the current selection of projects, perhaps highlighting specially the resources pertaining to the focal project. |
