#1462 closed enhancement (fixed)
better control of milestone: a way to 'reset' a milestone
Reported by: | anonymous | Owned by: | daan |
---|---|---|---|
Priority: | normal | Component: | ScrumBurndownPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.10 |
Description
is there a way to 'reset' a milestone, so that it starts "today" instead of yesterday? It is useful to see the milestone burndown totals as we are entering estimates, but if estimation takes the team more than a day (because some team members aren't synced), it would be nice to be able to reset to day 0 without db hacking.
Attachments (0)
Change History (5)
comment:1 Changed 17 years ago by
Summary: | better control of milestone → better control of milestone: a way to 'reset' a milestone |
---|
comment:2 Changed 16 years ago by
Owner: | changed from Sam Bloomquist to daan |
---|
comment:3 Changed 16 years ago by
Better yet, it would be handy being able to edit the start date for a milestone to any point in time...
The same way one can define the end date for a milestone, it would be nice to add the option to define it's start date.
comment:4 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
(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
comment:5 Changed 15 years ago by
k i got an update on my milestone to 2.o.1 after i wipe everything n reboot i cant sign on to my google account it says setup wizard is not working please try again....is there a way to fix this cuz now i cant do anything.......please help
Such soution is partly impelmented in the ticket #1510. Implementation includes:
changes to burndown.by in def process_request
in def start_milestone
Then add Restart button to template: