Changes between Version 32 and Version 33 of ProjectPlanPlugin
- Timestamp:
- Mar 22, 2016, 10:25:30 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProjectPlanPlugin
v32 v33 6 6 7 7 This plugin provides automatic visualizations of the ticket set used in the project (filterable). 8 This should overcome the problems that appear while organizing many developers or many tickets.9 Th e main contribution of this plugin is to provide (configurable, graphical)overview of ticket types, states, owners, dates and priorities.8 This should overcome the problems that appear while managing many developers or many tickets. 9 This plugin provides a configurable and graphical overview of ticket types, states, owners, dates and priorities. 10 10 11 11 The plugin introduces the following ticket attributes: … … 14 14 * '''dependencies''': tickets that have to be closed before the current ticket 15 15 16 These attributes are used to draw , e.g.networks of tickets representing the suggested (topological) order of the tickets.16 These attributes are used to draw for example networks of tickets representing the suggested (topological) order of the tickets. 17 17 Furthermore, it is a development base for several representations. 18 18 The architecture enables contributors to add their own visualizations. … … 92 92 93 93 === 1. Install the plugin 94 94 95 * check out the source code (you can also use export instead of checkout): 95 96 {{{#!sh 96 svn checkout http ://trac-hacks.org/svn/projectplanplugin/0.11/trunk97 svn checkout https://trac-hacks.org/svn/projectplanplugin/0.11/trunk 97 98 }}} 98 99 * run on the shell: … … 104 105 This plugin can be installed globally via: 105 106 {{{#!sh 106 easy_install http ://trac-hacks.org/svn/projectplanplugin/0.11/trunk107 easy_install https://trac-hacks.org/svn/projectplanplugin/0.11/trunk 107 108 }}} 108 109 … … 171 172 === 6. Macro Arguments 172 173 173 * The default settings {{{[[ProjectPlan()]]}}} produce a Hi rarchical MPM-Network with Version on toplevel, Milestone in Versions and Tickets as leafs in Milestones. All Tickets will be used for dependency, critical path and other calculations and visualisations.174 * The default settings {{{[[ProjectPlan()]]}}} produce a Hierarchical MPM-Network with Version on toplevel, Milestone in Versions and Tickets as leafs in Milestones. All Tickets will be used for dependency, critical path and other calculations and visualisations. 174 175 * Several macro parameter control the visualization, calculation and ticket filters/queries. 175 176 * A list of macro parameters can be found [wiki:ProjectPlanPlugin/MacroArgs here].