5 | | !ProjectPlan introduces time, dependency Fields and enables Project Management Features, especially for graphical visualisation, like Reports and Networks. Furthermore its a Development Base for several graphical Representations. |
| 7 | The !ProjectPlan plug-in provides 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 | The main contribution of this plug-in is to providing (configurable, graphical) overview of ticket types, states, owners, dates and priorities. |
7 | | * Current Testing Version is 0.60a (alpha) |
| 11 | |
| 12 | The plug-in introduces three ticket attributes: |
| 13 | * ''time to assign'': by the project plan at the latest at this date the owner of the ticket should start working on the task |
| 14 | * ''time to close'': by the project plan at the latest at this date the ticket should be closed |
| 15 | * ''dependencies'': tickets that have to be closed before the current ticket |
| 16 | These attributes are used to draw, e.g. networks of tickets representing the suggested (topological) order of the tickets. |
| 17 | Furthermore, it is a development base for several representations. |
| 18 | The architecture enables contributors to add their own visualizations. |
| 19 | |
| 20 | * Current Testing Version is 0.70b (beta) |
27 | | 1. Install the Plugin, either Global or Local (Local is recommended at this point) |
28 | | 2. Setup '''Ticket-Custom Fields''' in your Projects ''trac.ini'' |
29 | | * For the case, you already have Dependency, Assign/Close Date Ticket-Custom Fields |
30 | | * Add the Fieldnames (as long as the format is compatible) with |
| 41 | === 1. Install the plug-in === |
| 42 | * run on the shell |
| 43 | {{{ |
| 44 | python setup.py bdist_egg |
| 45 | }}} |
| 46 | * deploy the created egg either globally or locally (locally is recommended at this point) |
| 47 | |
| 48 | === 2. Setup '''Ticket-Custom Fields''' === |
| 49 | * in your projects ''trac.ini'' |
| 50 | * For the case, you already have dependency, assign/close date ticket-custom fields |
| 51 | * Add the field names (as long as the format is compatible) with |
51 | | 3. Basic !GraphViz Configuration (needed for Networks): |
52 | | * login with administrative Rights, navigate to Admin (WebAdmin) |
53 | | * Select the Panel !ProjectPlan -> General Settings (on the left) |
54 | | * Verify the Settings for '''cachepath''' and '''dot_executable''' |
| 72 | |
| 73 | === 3. Basic !GraphViz Configuration (needed for networks) === |
| 74 | |
| 75 | * login with administrative rights, navigate to admin (WebAdmin) |
| 76 | * select the panel ''!ProjectPlan -> General Settings'' (on the left) |
| 77 | * verify the settings for '''cachepath''' and '''dot_executable''' |
68 | | * Select the Panel !ProjectPlan -> Color Settings (on the left) |
69 | | * Set HTML Color codes and apply Settings |
70 | | |
71 | | 5. Image Setup |
72 | | * login with administrative Rights, navigate to Admin (WebAdmin) |
73 | | * Select the Panel !ProjectPlan -> Image Settings (on the left) |
74 | | * Select the Images, you'd like to use (the 16x16pixel images can reduce the network size) and apply Settings |
| 98 | * select the panel ''!ProjectPlan -> Image Settings'' (on the left) |
| 99 | * select the images, you'd like to use and apply settings |
| 100 | * the smaller images (e.g., 16x16 pixel) can reduce the size of the graphical network representation |
90 | | 1. Both Network (hierarchical and non-hierarchical) use critical path analysis. |
91 | | This wont work without ticket times for '''all''' tickets (either start,end, or both). |
92 | | 2. The critical path analysis wont work with cyclic dependencies |
93 | | 3. Dependencies are saved in Ticket-Custom fields. A dependency line consists of Ticket Identifiers "#<Ticket ID>". |
| 117 | 1. Both networks (hierarchical and non-hierarchical) use critical path analysis. |
| 118 | This won't work without ticket times for '''all''' tickets (either start, end, or both). |
| 119 | 2. The critical path analysis won't work with cyclic dependencies |
| 120 | 3. Dependencies are saved in ticket-custom fields. A dependency line consists of Ticket Identifiers "#<Ticket ID>". |