Changes between Version 14 and Version 15 of ProjectPlanPlugin


Ignore:
Timestamp:
Jan 16, 2010, 12:59:54 AM (5 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjectPlanPlugin

    v14 v15  
     1[[PageOutline]]
     2
    13= Project Plan Plugin =
    24
    35== Description ==
    46
    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.
     7The !ProjectPlan plug-in provides visualizations of the ticket set used in the project (filterable).
     8This should overcome the problems that appear while organizing many developers or many tickets.
     9The main contribution of this plug-in is to providing (configurable, graphical) overview of ticket types, states, owners, dates and priorities.
    610
    7   * Current Testing Version is 0.60a (alpha)
     11
     12The 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
     16These attributes are used to draw, e.g. networks of tickets representing the suggested (topological) order of the tickets.
     17Furthermore, it is a development base for several representations.
     18The architecture enables contributors to add their own visualizations.
     19
     20  * Current Testing Version is 0.70b (beta)
    821    * Features
    922      * !GraphViz based MPM Network
     
    1326      * Other small things
    1427    * Known Problems
    15       * not all/good Images for this Package
    1628      * possible unused Imports in several Modules
    1729      * Other small things in code and documentation
    1830
    1931== Software Requirements ==
     32
    2033 * Python 2.5 or 2.6 with Python Standard Library
    2134 * a recent !GraphViz Package
    2235 * Trac 0.11 (.1-5)
    23  * XML Template Engine Genshi 0.51 or compatible (is part of Trac 0.11)
     36 * XML Template Engine Genshi 0.51 or compatible (it is part of Trac 0.11)
     37
    2438
    2539== Basic Setup ==
    2640
    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   {{{
     44python 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
    3152   {{{
    3253[pp_options]
     
    3556custom_due_close_field = <your close Date fieldname>
    3657   }}}
    37     * This lets ProjectPlanPlugin use these configured fields
    38    * If you dont have corresponding Dependency and Date Fields, they need to be added as Ticket-Custom Fields
     58    * This lets !ProjectPlanPlugin use these configured fields
     59   * If you dont have corresponding dependency and date fields, they need to be added as ticket-custom fields
    3960   {{{
    4061[ticket-custom]
     
    4970   }}}
    5071
    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'''
    5578  * or set the following options in the projects trac.ini
    5679    {{{
     
    5982dot_executable = <path to graphviz binaries>\dot.exe
    6083    }}}
    61     * restart your webserver for configuration reload
    62   * Verify access and execution rights for the webserver User
     84    * restart your web server for configuration reload
     85  * verify access and execution rights for the web server User
    6386  * '''cachepath should be a separate directory for each project, this reduces possible cache collisions'''
    6487
    6588
    66  4. Color Setup:
     89=== 4. Color Setup ===
     90
     91  * login with administrative rights, navigate to admin (WebAdmin)
     92  * select the panel ''!ProjectPlan -> Color Settings'' (on the left)
     93  * set HTML color codes and apply settings
     94
     95=== 5. Image Setup ===
     96
    6797  * login with administrative Rights, navigate to Admin (WebAdmin)
    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
    75101
    76102== Daily Usage ==
    77103
    78  * The Cache size can grow quite big because Changes in Tickets and per User/Macro produce a lot of files and images
     104 * The cache size can grow quite big because changes in tickets and per user/macro produce a lot of files and images
    79105   * it is recommended to either wipe the cache in intervals or setup a daily cronjob to for cache cleaning
    80106
    81107== Example ==
    82 Add Ticket dependencies and close/assign Times. [[BR]]
     108
     109Add ticket dependencies and close/assign Times. [[BR]]
    83110  * Network Graphics
    84     * Use the '''!ProjectPlan''' Macro for (mpm like) Network graphics with several options enabling Project runtime estimation and (workload based) critical path analyses.
     111    * Use the '''!ProjectPlan''' Macro for (mpm like) network graphics with several options enabling project runtime estimation and (workload based) critical path analyses.
    85112  * Special Reports
    86     * Use special Reports which show Delays and Slacktimes
     113    * Use special reports which show delays and slacktimes
    87114  * ...
    88115
    89116Macro Samples:
    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>".
    94121    * Sample Dependencies: ''#6 and #5,#3 #4''
    95122