Changes between Version 47 and Version 48 of SimpleMultiProjectPlugin
- Timestamp:
- Mar 12, 2015, 9:51:36 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SimpleMultiProjectPlugin
v47 v48 1 1 [[PageOutline(2-5,Contents,pullout)]] 2 2 3 = SimpleMultiProjectPlugin =3 = SimpleMultiProjectPlugin 4 4 5 == Description == 5 == Description 6 6 7 Lets you easily '''manage multiple user projects with one Trac instance''' or, respectively, one Trac database (.db file). 7 8 … … 15 16 Note: The Multiple Project feature in the sense of having a meta Trac project on top of several Trac projects is discussed in T:#130 and scheduled for [T:milestone:topic-multiproject Trac topic-multiproject] which is eventually part of [T:milestone:next-dev-1.1.x Trac next-dev-1.1.x]. 16 17 17 == Plan == 18 in testing state: 18 == Plan 19 20 In testing state: 21 19 22 [[TicketQuery(component=SimpleMultiProjectPlugin&keywords=~testing)]] 20 23 21 work in progress: 24 Work in progress: 25 22 26 [[TicketQuery(component=SimpleMultiProjectPlugin&keywords$=planned&status=assigned|reopened)]] 23 27 24 still just an idea: 28 Still just an idea: 29 25 30 [[TicketQuery(component=SimpleMultiProjectPlugin&keywords$=planned&status!=assigned|reopened|closed)]] 26 31 27 == Technical thoughts ==32 == Technical thoughts 28 33 29 34 This plugin adds a new resource 'project' implemented by database table: 30 1. smp_project: a list of all defined projects 31 Actually, most database tables of Trac core related to resources would need a new column 'project_id'. This way tickets, components, milestones, versions or even wikis could attach to certain projects. Since a plugin just adds stuff but cannot change the core structure, it implements the new dimension 'project' not by adding a new column to each resource table but rather by adding several mapping tables smp_[resource]_project, each one mapping a certain resource to projects:32 2. smp_milestone_project: the association of milestones to projects33 3. smp_version_project: the association of versions to projects34 4. smp_component_project: the association of components to projects35 1. smp_project: a list of all defined projects[[BR]] 36 Actually, most database tables of Trac core related to resources would need a new column 'project_id'. This way tickets, components, milestones, versions or even wikis could attach to certain projects. Since a plugin just adds stuff but cannot change the core structure, it implements the new dimension 'project' not by adding a new column to each resource table but rather by adding several mapping tables smp_[resource]_project, each one mapping a certain resource to projects: 37 1. smp_milestone_project: the association of milestones to projects 38 1. smp_version_project: the association of versions to projects 39 1. smp_component_project: the association of components to projects 35 40 36 == Example ==41 == Example 37 42 38 43 '''''Admin Interface''''': … … 74 79 [[Image(timeline_projects_filter.png)]] 75 80 76 == Bugs/Feature Requests ==81 == Bugs/Feature Requests 77 82 78 83 total issue record: … … 84 89 [http://trac-hacks.org/newticket?component=SimpleMultiProjectPlugin&owner=falkb new ticket]. 85 90 86 == Download ==91 == Download 87 92 88 93 Download the zipped source from [download:simplemultiprojectplugin here]. 89 94 90 == Source ==95 == Source 91 96 92 97 You can check out SimpleMultiProjectPlugin from [http://trac-hacks.org/svn/simplemultiprojectplugin here] using Subversion, or [source:simplemultiprojectplugin browse the source] with Trac. 93 98 94 == Installation ==99 == Installation 95 100 96 101 1. Add a custom ticket field 'project' in your trac.ini to give tickets the information to which project they belong. Milestones selection depends on that as well. … … 136 141 137 142 '''Author:''' [wiki:crossroad], [wiki:falkb], [wiki:thomasd] [[BR]] 138 '''Maintainer:''' [ wiki:falkb] [[BR]]143 '''Maintainer:''' [[Maintainer]] [[BR]] 139 144 '''Contributors:'''