Changes between Version 5 and Version 6 of ScrumBurndownPlugin


Ignore:
Timestamp:
Jun 23, 2006, 9:21:29 PM (8 years ago)
Author:
sambloomquist
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ScrumBurndownPlugin

    v5 v6  
    88
    99Installing this plugin is a four-step process.
    10  1. Apply this patch to enable the 'integer' ticket field type
     10 1. Apply this [LinkComingSoon patch] to enable the 'integer' ticket field type
    1111 1. Add custom ticket fields
    1212 1. Install the egg
    1313 1. Create a cron/pycron job to run a daily python script
    1414
    15 === Add custom ticket fields ===
     15==== Add custom ticket fields ====
    1616Add the following to your trac.ini file:
    1717
     
    3131Original estimate is not really used by the plugin, it's just common Scrum process to be able to see how the estimates have change throughout a given sprint.
    3232
    33 === Installing the egg ===
     33==== Installing the egg ====
    3434Install just like you would any other Trac plugin.  Drop the egg into your plugins or site-packages folder and then try to access Trac in your browser.  You will get an error message saying that the database needs to be upgraded and telling you the trac-admin command to do it.  (I think it's something like 'trac-admin !YourProjectName.db upgrade').  Perform the upgrade.
    3535
    36 === Pycron/cron job ===
    37 Download the this file: attachment:burndown_job.py and place it into a directory where you can run it with python.  For example, C:\Python23\Scripts\
     36==== Pycron/cron job ====
     37Download the this file: attachment:burndown_job.py and place it into a directory where you can run it with python.  For example, "C:\Python23\Scripts\"
    3838
    3939Set up a job to run the burndown_job.py script once a day.  I personally am using Windows, so I used pycron.  Here is an example pycron tab file to run the job at noon on weekdays: attachment:crontab.txt