better control of milestone: a way to 'reset' a milestone

[anonymous]

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.

[Tatyana Tvardovskaya]

Such soution is partly impelmented in the ticket #1510. Implementation includes:

changes to burndown.by in def process_request

		
        if 'restart' in req.args:
			self.start_milestone(db, selected_milestone, False)
        elif 'start' in req.args:
			self.start_milestone(db, selected_milestone, True)
        else:
			data['draw_graph']= True
			data['burndown_data']=self.get_burndown_data(db, selected_milestone, components, selected_component)
			# this will be a list of (id, hours_remaining) tuples

in def start_milestone

    def milestone_start(self, db, milestone):
		cursor = db.cursor()
		cursor.execute("SELECT started FROM milestone WHERE name = '%s'" % milestone)
		row = cursor.fetchone()
		if row and (row[0] > 0):
			return row[0]
		else:
			return 0
		
    def start_milestone(self, db, milestone, savestart):	
		start_date = self.milestone_start(db, milestone)
		if (savestart and start_date > 0):
			raise TracError("Milestone '%s' was already started on %s" % (milestone, format_date(int(start_date))))
			
		cursor = db.cursor()
		cursor.execute("UPDATE milestone SET started = %i WHERE name = '%s'" % (int(time.time()), milestone))
		db.commit()

Then add Restart button to template:

<input type="submit" name="restart" value="Restart Milestone Now!" />

[Filipe Correia]

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.

[daan]

(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

[kfcxuexiong@…]

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