Changes between Version 66 and Version 67 of SimpleMultiProjectPlugin
- Timestamp:
- Jul 30, 2016, 2:58:14 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SimpleMultiProjectPlugin
v66 v67 10 10 11 11 Key features: 12 * Milestones and versions are assigned to their projects, and both are displayed on the roadmap. There are several possibilities to filter by projects on that page, and also the timeline. 12 * Milestones and versions are assigned to their projects, and both are displayed on the roadmap. 13 * On the roadmap page and timeline page it is possible to apply filters to show only projects that meet certain criteria. 13 14 * Components can be assigned to all or only certain projects. 14 15 * 'New Ticket' will just offer the associated milestones, versions and components of the chosen project. This requires a new custom-ticket field 'project'. 15 * You can rectrict access to certain milestones, versions and tickets by defining members or non-members of a project.16 17 This is already running stable in some realproduction environments.16 * Restrict access to certain milestones, versions and tickets by defining members or non-members of a project. 17 18 This plugin is already running stable in production environments. 18 19 19 20 '''Note''': The Multiple Project feature in the sense of having a meta Trac project on top of several Trac projects is discussed in T:#11025 (formerly T:#130) and the unscheduled milestone [T:milestone:topic-multiproject Trac topic-multiproject]. 20 21 21 22 === Integration with other plugins 23 22 24 MultiProjectBacklogPlugin integrates with this plugin allowing you to maintain project specific backlogs in your agile process. 23 25 24 26 When ExtendedVersionPlugin is installed SimpleMultiProjectPlugin adds an additional ''Version'' column to the milestone table of the milestone admin page. 27 25 28 === Plan 26 29 … … 39 42 [[TicketQuery(component=SimpleMultiProjectPlugin&keywords$=planned&status!=assigned|reopened|closed)]] 40 43 41 === Technical thoughts44 === Technical implementation details 42 45 43 46 This plugin adds a new resource 'project' implemented by database table: … … 55 58 56 59 57 [[Image(admin_project.png, 400px)]]58 59 ---- 60 61 Add project summary and description. This is displayed on the roadmap page then:62 63 64 [[Image(admin_projects_modify.png, 400px)]]60 [[Image(admin_project.png, 50%)]] 61 62 ---- 63 64 Add project summary and description. This is displayed on the roadmap page as follows: 65 66 67 [[Image(admin_projects_modify.png, 50%)]] 65 68 66 69 ---- … … 76 79 * Note: "New Ticket" with a chosen project only offers milestones and versions mapped to that certain project. 77 80 78 [[Image(edit_milestone.png, 400px)]]81 [[Image(edit_milestone.png, 50%)]] 79 82 80 83 ---- … … 83 86 84 87 85 [[Image(roadmap_projects_filter.png, 400px)]]88 [[Image(roadmap_projects_filter.png, 50%)]] 86 89 87 90 ---- … … 90 93 91 94 92 [[Image(timeline_projects_filter.png, 400px)]] 93 94 ---- 95 You also can include the Project Name in your Ticket Queries by adding a join to "ticket_custom". 96 Example: 95 [[Image(timeline_projects_filter.png, 50%)]] 96 97 ---- 98 You also can include the Project Name in your Ticket Queries by adding a join to the `ticket_custom` table: 97 99 98 100 {{{#!sql 99 101 SELECT p.value AS __color__, 100 102 id AS ticket, summary, 101 tc.value AS 'Project-Name', #display the Project Name in the Ticket Overview103 tc.value AS 'Project-Name', -- display the Project Name in the Ticket Overview 102 104 version, milestone, t.type AS type, 103 105 owner, status, … … 105 107 changetime AS _changetime, description AS _description, 106 108 reporter AS _reporter 107 108 LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority'109 LEFT JOIN ticket_custom tc ON t.id = tc.ticket AND tc.name = 'project' # add thejoin to ticket_custom and only select the Project-Name110 111 109 FROM ticket t 110 LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority' 111 LEFT JOIN ticket_custom tc ON t.id = tc.ticket AND tc.name = 'project' -- join to ticket_custom and only select the Project-Name 112 WHERE status <> 'closed' 113 ORDER BY CAST(p.value AS integer), milestone, t.type, time 112 114 }}} 113 115 … … 164 166 - {{{ john, mary, group1, authenticated }}} to restrict to this set of users 165 167 - {{{ !, bob, anonymous, group2 }}} to exclude from the project. 166 [[BR]]167 168 168 169 == Configuration 169 The plugin comes with sane default values but if you have specific requirements you may change some configuration options. 170 171 The plugin comes with sane default values, but if you have specific requirements you may change some configuration options. 170 172 171 173 When ExtendedVersionPlugin is installed an additional column with version information is added to the milestone table on the admin page. You may remove this column just by disabling the plugin {{{SmpAddExtendedVersionColumn}}}. Use the plugin admin panel or add the following line to your configuration file: … … 176 178 177 179 There are some `trac.ini` options to control association of projects with milestones and components. 178 1. 180 1. Creation of milestones is only possible when a project is chosen. You may disable this behaviour by setting the following in `trac.ini`: 179 181 {{{#!ini 180 182 [simple-multi-project] 181 183 milestone_without_project = True 182 184 }}} 183 1. 185 1. To ensure only a single project is associated with each milestone set the following in `trac.ini`: 184 186 {{{#!ini 185 187 [simple-multi-project]
