Ticket #1800 (closed defect: fixed)

Opened 3 years ago

Last modified 1 year ago

No chart when clicking Burndown chart button.

Reported by: plafoucriere@kamayo.com Assigned to: daan
Priority: normal Component: ScrumBurndownPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.11

Description

I just installed the plugin, and it seems to work, except that I can't the charts working. I'm using trac 0.10.3 on a debian etch, with python 2.4.4 (debian's default) and ScrumBurndown? plugin version 01.08.10 and TimeAndEstimationPlugin? version http://trac-hacks.org/changeset/latest/timingandestimationplugin/branches/trac0.10?old_path=/&filename=timingandestimationplugin/branches/trac0.10&format=zip

Installation went OK, and I have the buttons Management and Burndown in trac.

Thus, when I click on a milestone, and select the Start Milteston button, nothing happens. The database is updated (milestone table), but I can't see the Complete miltestone button. Moreover, The chart will never display.

Thanks

Attachments

Picture 3.png (21.1 kB) - added by plafoucriere@kamayo.com on 07/16/07 20:23:12.
broken chart

Change History

07/16/07 20:23:12 changed by plafoucriere@kamayo.com

  • attachment Picture 3.png added.

broken chart

07/19/07 11:23:58 changed by anonymous

Apparently, I still have to run the script burndown_job.py every day, even if I'm using version 01.08.10. I thought this version was supposed to update automatically the graph.

I'm leaving the ticket open since this is not the expected process.

09/09/07 12:30:42 changed by cerw@nano.cz

So we still need to use cron? for each trac?

09/14/07 21:23:12 changed by robert@kuropkat.com

So, what's up with this one? I have the same problem. Notice from the image there is no Milestone Complete button either. What do we need to do?

Also, when I try running the burndown_job.py script it says:

first run of burndown_job.py today - insert needed

What does that mean? I notice after running it my display changed somewhat.

Note: We just setup trac for the first time and in the process of doing so "finished" a two week cycle, so some of the screwiness I am seeing may be due to the fact we have not done all the proper data entry. however, the missing button for completing a milestone concerns me...

Robert Kuropkat

12/19/07 14:17:55 changed by anonymous

I saw this too. Here's what's really up, the chart does not start updating until the day after you start the milestone (and then it doesn't actually change until one of its tickets is modified).

So the workaround is ignoring the messed up chart for a day.

12/28/07 23:49:57 changed by rangerden@rangersps.org

Ok, another datapoint. I had the same symptoms: no "finish milestone" button present, char initially not drawn. I tried running burndown_job.py manually, and the chart appeared. Note that my experience was not the same as reported by anonymous on 12/18/2007, in that I waited two days after starting the milestone and still saw no chart. When I ran burndown_job.py, it stated that an insert was needed, which looks to me to indicate that it had never run before. I am using Trac 0.11b and sqlite.

10/17/08 08:45:35 changed by daan

  • owner changed from sambloomquist to daan.

10/21/08 13:34:15 changed by anonymous

same versions, same symptoms here, until I run the burndown_job.py and additionnaly it said : 

/var/lib/python-support/python2.4/trac/loader.py:96: UserWarning: Module burndown was already imported from /tmp/scrumburndownplugin/burndown/__init__.pyc, but /trac/plugins/TracBurndown-01.08.10-py2.4.egg is being added to sys.path
  egg.activate()
burndown_job.py has already been run today - update needed

having only 1 daily update is really disappointing..

10/21/08 14:13:30 changed by daan

  • release changed from 0.10 to 0.11.

burndown_job.py has already been run today - update needed

This means that the burndown job will update the values instead of inserting them (this is a notification, not an error). You can run the burndown job as often as you like (we run it once an hour).

I will look into these problems.

12/18/08 10:24:39 changed by anonymous

Maybe check your trac.ini for correct 

[trac]
base_url

Was wrong in my system.

12/25/08 11:43:42 changed by daan

  • status changed from new to closed.
  • resolution set to fixed.

(In [5058]) Release of version 1.9.1 of the Trac Scrum burndown plugin. See http://stuq.nl/weblog/2008-12-25/scrum-burndown-plugin-191-released for more information.

A new version of the Scrum Burndown plugin for Trac is released, bringing compatibility for PostgreSQL, MySQL, Trac 0.11.2.1, and many bug fixes. Upgrading is recommended.

New features The Scrum burndown plugin is currently compatible and tested with Trac 0.10.5, Trac 0.11.1, Trac 0.11.2.1 Python 2.4 and Python 2.5. Additional to the previous SQLite compatibility, support for both PostgreSQL 8.3 and MySQL 5 has been added.

The following issues are fixed:

  • Fixes #1462 better control of milestone: a way to ‘reset’ a milestone
  • Fixes #1217 database upgrade fails after installing latest scrumburndownplugin
  • Fixes #2476 Error: ‘line_graph’ is undefined - stop graph from displaying
  • Fixes #1730 couldn’t upgrade
  • Fixes #2729 Error while running under PostgreSQL
  • Fixes #3102 burndown_job.py fails INSERT NULL id
  • Fixes #1909 Overshooting estimate reduces remaining effort while ticket is open
  • Fixes #1189 TracBurndown?-01.05.10-py2.4.egg error
  • Fixes #1800 No chart when clicking Burndown chart button.
  • Fixes #4047 AttributeError?: ‘NoneType?’ object has no attribute ‘getValue’
  • Fixes #2224 Changing ticket component causes removal from burndown
  • Fixes #2562 Creating a new component breaks the burndown graphic for “All Components”
  • Fixes #4222 Install fails on mysql
  • Fixes #2218 ScrumBurndownPlugin, trac 0.10.4, mysql

Add/Change #1800 (No chart when clicking Burndown chart button.)




Change Properties
Action