Changes between Version 5 and Version 6 of ScrumBurndownPlugin

Timestamp:

Jun 23, 2006, 7:21:29 PM (17 years ago)

Author:

Sam Bloomquist

Comment:

--

ScrumBurndownPlugin

@@ -8 +8 @@
 
 Installing this plugin is a four-step process.
- 1. Apply this patch to enable the 'integer' ticket field type
+ 1. Apply this [LinkComingSoon patch] to enable the 'integer' ticket field type
  1. Add custom ticket fields
  1. Install the egg
  1. Create a cron/pycron job to run a daily python script
 
-=== Add custom ticket fields ===
+==== Add custom ticket fields ====
 Add the following to your trac.ini file:
 
@@ -31 +31 @@
 Original 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.
 
-=== Installing the egg ===
+==== Installing the egg ====
 Install 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.
 
-=== Pycron/cron job ===
-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\
+==== Pycron/cron job ====
+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\"
 
 Set 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