ticket summary type release owner status created modified _description _reporter 637 Have a capacity line in the chart when the due date of a milestone is set enhancement 0.10 daan new 2006-08-22T11:58:30+02:00 2008-10-17T08:48:27+02:00 "Hi, I made some additions to your ScrumBurndownPlugin in order to support a capacity line. It draws an additional line when the milestone due date is set. (calculate the difference between start and due date, and adds the line with a seperate array of points) [[BR]] If you're intrested I can provide a patch. (this will include some additional fixes, like setting the current_estimate to 0 when a ticket is closed (in the burndown_job) and not displaying a chart when there is no data. " Olger Warnier 1249 Let the whole timeline be shown enhancement 0.10 daan new 2007-02-25T10:42:28+01:00 2010-05-04T17:12:24+02:00 It would be great if we could see the whole timeline from the very beginning so that we would always see what we're approaching to (in terms of # of days). In other words, the whole X-axis should be shown from the very beginning so that we would always know if our work efforts are close to the ideal or not. tote 1626 Allow filter milestones in burndown chart enhancement 0.10 daan new 2007-06-07T12:17:43+02:00 2008-10-17T08:45:51+02:00 "I't would be nice if we can exclude some milestones in the burndown chart's combo. It's necesary when we have a lot of finished milestones." jmnavarro@… 4413 Collecting data for milestones that were not yet started enhancement 0.11 daan assigned 2009-01-09T10:54:32+01:00 2009-01-15T10:59:24+01:00 "With the implementation of ticket #1462 we can now set a new start date for a give milestone, which is great, but I'm now not sure how should the chart behave when this feature is used... I tried defining a start date for a milestone that has started a few weeks ago, and was expecting to see a chart for this entire period when selecting the right milestone on the burndown tab. However, what happens is that the chart for this milestone keeps being displayed as it was started today, even though it does contain some previously closed tickets. I think I understand why this happens (please confirm): the chart data is actually stored as we go adding time and closing tickets, so even if we change the start date, the 'historical' data as registered by the ScrumBurndownPlugin won't be affected, and the plotted chart will be the same. In spite of this, I still wish I could see the burndown for milestones that have started before the plugin was in use, and even for milestones that have already been closed, as it may allow to better understand the project's work-cycle, and better plan for the future. My suggestion (not sure if this is even doable) is that the chart is plotted on the fly, from the TimingAndEstimationPlugin data (estimated hours and total hours) and from the ticket data (which milestone does it belong to, when was it added and when was it closed), instead of keeping historical data specific for ScrumBurndownPlugin. Something that may become an issue with this approach is that tickets that are removed or added after the milestone's start date won't be reflected on the burndown chart (btw, this was also an issue discussed in ticket #1292). However, maybe it's not that bad to allow modifying a chart on a past time-frame; after all, if we think of a milestone as a sprint, adding and removing tickets should be avoided as much as possible, so, when it does happen, it is probably to correct some misuse of trac, and make it reflect what really happened. " Filipe Correia 4925 ScrumBurndownPlugin integration with TracHoursPlugin enhancement 0.11 daan new 2009-04-15T16:40:51+02:00 2009-04-15T16:40:51+02:00 The ScrumBurndownPlugin should integrate with the TracHoursPlugin method of doing time tracking instead of only working with the TimingAndEstimationPlugin. anonymous 11342 Scrum burndown as macro enhancement Sam Bloomquist new 2013-10-07T14:17:27+02:00 2013-10-07T14:17:27+02:00 It would be nice if you could make a ScrumBurndown macro out of this to allow users to place burndowns everywhere in trac. anonymous 3723 Ideal burndown line enhancement 0.11 daan new 2008-09-15T11:29:23+02:00 2008-10-21T18:04:49+02:00 "Would be great having an ideal-burndown line being plotted. Something similar to what agilo does (http://media.agile42.com/content/Burndown_Chart_of_Agilo_for_Scrum.png), but not requiring all of agilo's other features, which, i believe, aren't really needed (at least, for me they aren't). " Filipe Correia 11628 """hours remaining"" can not show" defect Sam Bloomquist new 2014-03-17T03:34:09+01:00 2014-03-17T03:34:09+01:00 "when use ScrumBurndownPlugin the ""hours remaining"" is wrong " anonymous 4381 UnicodeDecodeError with Trac-0.11 defect 0.11 daan assigned 2009-01-05T15:41:27+01:00 2012-02-01T05:50:46+01:00 "I have installed the ""Timing and Estimation Plugin"" without any problems and everything was working. After installation of the ""Scrum Burndown Plugin"" I see this error, when I click on the ""Burndown"" menu entry: {{{ Traceback (most recent call last): File ""/usr/lib/python2.5/site-packages/Trac-0.11-py2.5.egg/trac/web/api.py"", line 339, in send_error 'text/html') File ""/usr/lib/python2.5/site-packages/Trac-0.11-py2.5.egg/trac/web/chrome.py"", line 726, in render_template stream.render(method, doctype=doctype, out=buffer) File ""build/bdist.linux-i686/egg/genshi/core.py"", line 179, in render File ""build/bdist.linux-i686/egg/genshi/output.py"", line 61, in encode File ""build/bdist.linux-i686/egg/genshi/output.py"", line 311, in __call__ File ""build/bdist.linux-i686/egg/genshi/output.py"", line 753, in __call__ File ""build/bdist.linux-i686/egg/genshi/output.py"", line 592, in __call__ File ""build/bdist.linux-i686/egg/genshi/output.py"", line 707, in __call__ UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 1155: ordinal not in range(128) }}} As you can imagine, with this error, the plugin is useless for us... Btw, trac default character set is UTF-8 (we use German Umlauts)." oliver.mueller@… 4667 Burndown only shows 2 days and not the days of sprint defect 0.11 Sam Bloomquist new 2009-02-20T00:30:59+01:00 2012-02-01T02:46:13+01:00 "Hello I've just installed the timeandestimating pluging and then the scrumburndownplugin. Then I've done estimating the tickets of milestone ""Sprint 1"". When I go to the burndown chart, it shows remaining hours and only 2 days of the sprint. Should the chart not show all days of sprint? " cmenzi@… 5590 Burndown table not getting updated for certain milestones defect 0.11 Sam Bloomquist new 2009-07-30T11:38:26+02:00 2009-07-30T11:38:26+02:00 "I installed the latest burndown plugin & observed that burndown graphs are displaying only for couple of milestones & not for other milestones. I checked the sqlite database at back end & observed that entries are not present for other milestones. What could be reason for this?" amith 5583 No graph when no components are defined defect 0.11 daan new 2009-07-29T13:17:57+02:00 2009-07-29T13:17:57+02:00 " If there are no components defined there will be no burndown visible. That's very surprising and difficult to figure out without looking at the code. Would be nice to have a fix for that. Code (burndown.py), problem marked by XXX: {{{ def update_burndown_data(self): db = self.env.get_db_cnx() cursor = db.cursor() # today's date today = format_date(int(time.time())) milestones = dbhelper.get_milestones(db) components = dbhelper.get_components(db) for mile in milestones: if mile['started'] and not mile['completed']: # milestone started, but not completed XXX PROBLEM>>> for comp in components: XXXXX HERE: WHAT IF NO COMPONENTS?? XXXXX sqlSelect = ""SELECT est.value AS estimate, ts.value AS spent ""\ ""FROM ticket t ""\ }}} Thanks!" forum-mail@… 4517 Change method for computing burndown defect 0.11 daan new 2009-01-26T11:05:58+01:00 2009-02-10T17:17:26+01:00 "Opening ticket after discussion started here : http://stuq.nl/weblog/2008-12-25/scrum-burndown-plugin-191-released#comment-5468 The plugin currently calculates burndown as 'hours estimated for ticket - hours spent on ticket'. Per Scrum best practices, burndown should be only the 'estimated hours', and should not involve the actual hours spent on the task." adean@… 4603 Burndown and roadmap differs in amount of work remaining defect 0.11 daan new 2009-02-10T14:09:18+01:00 2009-02-18T11:24:26+01:00 "I don't know if this is by design or so, but I've got 360 hours remaining on a milestone in the roadmap, and only 89 hours showing by the burndown chart. I've looked at the burndown table and am thinking that it might be out-of-date somehow. Can I force a rebuild somehow, to see if that's the case? (Great plugin btw! :)" Marcus Lindblom 5891 Method to recover from Milestone renaming defect 0.11 Sam Bloomquist new 2009-09-29T03:16:10+02:00 2009-09-29T03:16:10+02:00 "It was decided to rename all our milestones and components mid-sprint. This appears to cause the burndown charts to cease to exist. I opened up the sqlite3 file and changed the burndown table entries to match the new names but the burndown chart page is still blank. I restarted Apache, still no joy. After reviewing the database tables, I'm not sure what else to fix. Everything matches the enum's but the charts are still not built. Can the charts be recovered? Any ideas on a work around? " Jhon Honce 6200 TracBurnDown does not work with custom workflow defect 0.11 daan new 2009-11-13T10:35:34+01:00 2009-11-13T10:35:34+01:00 "'''Problem''': [http://trac-hacks.org/wiki/ScrumBurndownPlugin TracBurnDown] does not work with custom workflow because burndown.py compares the status with a fixed set of values. '''Solution''': Follow the assumptions in [http://trac.edgewall.org/wiki/TracWorkflow TracWorkflow] and include every ticket that is not closed. Patch from [http://people.debian.org/~jps/squeeze preliminary Debian package] attached. " Jens Peter Secher 6233 needs_upgrade logic is flawed defect 0.11 Sam Bloomquist new 2009-11-19T11:24:52+01:00 2009-11-19T11:24:52+01:00 "The logic of the [source:scrumburndownplugin/trunk/burndown/burndown.py burndown.py] environment_needs_upgrade is flawed. If the `burndown` table does not exist, but the `milestone` table has a `started` field (created by an other plugin), the `needsUpgrade` is set to `False` See attached patch for improved logic" hans.bogaards@… 6478 Burndown Chart Not Displaying defect 0.11 daan new 2010-01-22T10:44:16+01:00 2010-01-22T15:13:26+01:00 "I can not get any Burndownchart to display. The milsestone is started. The report states ""Current effort remaining: 0 hours"" and the area where the chart should be displays a narrow area with numbers -51200 -38400 -25600 -12800 I get the following in my debug logs: {{{ 2010-01-22 10:36:29,041 Trac[main] DEBUG: Dispatching 2010-01-22 10:36:29,067 Trac[chrome] DEBUG: Prepare chrome data for request 2010-01-22 10:36:29,073 Trac[session] DEBUG: Retrieving session for ID 'fredrik' 2010-01-22 10:36:29,138 Trac[tande_filters] DEBUG: self.billing_reports= set([9, 10, 11, 12, 13, 14, 15, 16, 17]) 2010-01-22 10:36:29,139 Trac[ticket_webui] DEBUG: TicketWebUiAddon executing 2010-01-22 10:36:29,139 Trac[ticket_webui] DEBUG: TicketWebUiAddon not the correct template 2010-01-22 10:36:29,836 Trac[main] DEBUG: Dispatching 2010-01-22 10:36:29,841 Trac[chrome] DEBUG: Prepare chrome data for request 2010-01-22 10:36:29,846 Trac[session] DEBUG: Retrieving session for ID 'fredrik' 2010-01-22 10:36:29,851 Trac[tande_filters] DEBUG: self.billing_reports= set([9, 10, 11, 12, 13, 14, 15, 16, 17]) 2010-01-22 10:36:29,852 Trac[ticket_webui] DEBUG: TicketWebUiAddon executing 2010-01-22 10:36:29,852 Trac[ticket_webui] DEBUG: TicketWebUiAddon not the correct template }}}" anonymous 7026 Milestone complete button missing defect 0.11 daan new 2010-04-23T20:21:22+02:00 2010-04-23T20:21:22+02:00 "The burndown plugin is installed and working ok with our Trac 0.11.6 installation (using the patch outlined here http://trac-hacks.org/ticket/4504). I can start a milestone, and the graph displays ok. However, there is no ""Milestone complete"" button. My user account has BURNDOWN_ADMIN permissions, so it should be there I would think." guy 8342 Burndown chart displaying null data defect 0.11 daan new 2010-12-28T15:49:28+01:00 2010-12-28T15:49:28+01:00 "Using Scrum Burndown plugin 1.9.2 on trac 0.11.5 with timingandestimationplugin 0.9.0 we have the following problem (see attached image). In the Sprint I see both active and closed tickets and those tickets have set Estimated Hours, Total Hours (when finished), and Percent Complete, as well as other fields. Is this a bug or is there a setting we're missing?" cto@… 8789 TypeError: 'NoneType' object is not subscriptable defect 0.12 daan new 2011-05-11T22:58:46+02:00 2011-05-12T00:10:07+02:00 "==== How to Reproduce ==== While doing a GET operation on `/burndown`, Trac issued an internal error. I downloaded and installed the plugin via easy_install and giving the SVN location as specified on the page. This is what I did: {{{ C:\>easy_install http://trac-hacks.org/svn/scrumburndownplugin/ Downloading http://trac-hacks.org/svn/scrumburndownplugin/ Doing subversion checkout from http://trac-hacks.org/svn/scrumburndownplugin/ to c:\docume~1\admini~1\locals~1\temp\easy_install-aonx7g\scrumburndownplugin Processing scrumburndownplugin Running trunk\setup.py -q bdist_egg --dist-dir c:\docume~1\admini~1\locals~1\tem p\easy_install-aonx7g\scrumburndownplugin\trunk\egg-dist-tmp-vk_ngq zip_safe flag not set; analyzing archive contents... Adding tracburndown 1.9.2 to easy-install.pth file Installed c:\python27\lib\site-packages\tracburndown-1.9.2-py2.7.egg Processing dependencies for tracburndown==1.9.2 Finished processing dependencies for tracburndown==1.9.2 C:\>trac-admin C:\trac\poc upgrade Attempting to create the burndown table Attempting to modify the milestone table Upgrade of the Burndown plugin failed Error message: (1264, ""Out of range value for column 'due' at row 1"") Upgrade done }}} As you can see after running my environment upgrade I encountered this issue shown above. When I tried to use the plugin via Trac get: TypeError: 'NoneType' object is not subscriptable. Please see below for environment setting and python traceback. I have also attached my log file. Please advise. Request parameters: {{{ {} }}} User agent: `Opera/9.80 (Windows NT 5.2; U; en) Presto/2.8.131 Version/11.10` ==== System Information ==== || '''`Trac`''' || `0.12.3dev-r10683` || || '''`Babel`''' || `0.9.5` || || '''`FullBlog`''' || `0.1.1-r9430` || || '''`Genshi`''' || `0.6` || || '''`mod_wsgi`''' || `3.3 (WSGIProcessGroup WSGIApplicationGroup %{GLOBAL})` || || '''`MySQL`''' || `server: ""5.5.11"", client: ""5.1.50"", thread-safe: 1` || || '''`MySQLdb`''' || `1.2.3` || || '''`Python`''' || `2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit (Intel)]` || || '''`RPC`''' || `1.1.2-r9970` || || '''`setuptools`''' || `0.6c11` || || '''`jQuery`''' || `1.4.4` || ==== Enabled Plugins ==== || '''`duplicateticketsearch`''' || `1.0.1` || || '''`estimatorplugin`''' || `0.2.5` || || '''`timingandestimationplugin`''' || `1.1.3b` || || '''`tracburndown`''' || `1.9.2` || || '''`tracdiscussion`''' || `0.8-r9877` || || '''`tracexcelviewer`''' || `0.1` || || '''`tracfullblogplugin`''' || `0.1.1-r9430` || || '''`tracsectioneditplugin`''' || `0.1.1` || || '''`tractags`''' || `0.6` || || '''`tracvote`''' || `0.1.3` || || '''`tracwysiwyg`''' || `0.12.0.3-r9676` || || '''`tracxmlrpc`''' || `1.1.2-r9970` || ==== Python Traceback ==== {{{ Traceback (most recent call last): File ""build\bdist.win32\egg\trac\web\main.py"", line 517, in _dispatch_request dispatcher.dispatch(req) File ""build\bdist.win32\egg\trac\web\main.py"", line 238, in dispatch resp = chosen_handler.process_request(req) File ""build\bdist.win32\egg\burndown\burndown.py"", line 172, in process_request data['burndown_data'] = req.hdf['burndown_data'] = self.get_burndown_data(db, selected_milestone, components, selected_component) File ""build\bdist.win32\egg\burndown\burndown.py"", line 205, in get_burndown_data cursor.execute(sqlBurndown, (selected_milestone['name'], comp['name'])) TypeError: 'NoneType' object is not subscriptable }}}" chowell@… 4408 Chart line precision (dealing with fractions of an hour) defect 0.11 daan assigned 2009-01-09T06:53:29+01:00 2009-01-15T11:19:10+01:00 "Although one of my milestones has still half an hour to go, the burndown line is already touching the bottom of the chart (pls see the attached picture). At first, I though it might had something to do with issue #3490 of the TimingAndEstimationPlugin, but i've fixed that one (by upgrading pysqlite) and haven't seen any change on the chart, so it might not have anything to do with it." Filipe Correia