Modify

Opened 8 years ago

Closed 7 years ago

#498 closed enhancement (fixed)

make compatible with http://trac.edgewall.org/wiki/TimeTracking

Reported by: jan@… Owned by: sambloomquist
Priority: high Component: ScrumBurndownPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.9

Description

Nice work...and very interesting. But unfortunately, it is not compatible with the trac-extension http://trac.edgewall.org/wiki/TimeTracking due to different column names in the database. Nothing more i think, so resolving this problem should be easy, does it?

But just the combination of the 2 extensions/hacks would be a really great advantage for us.

Attachments (0)

Change History (7)

comment:1 Changed 8 years ago by sambloomquist

This is a good idea. Unfortunately, I'm a little swamped with other projects right now. I think I'll have some time to take a look at this in about a month.

comment:2 in reply to: ↑ description Changed 8 years ago by TimoPunkka

Replying to jan@motubo.com:

I hacked this in. You can do it by changing the parse_time function in roadmap.py of Time Tracking plugin to ignore h|m|min unit and allways force hours, and renaming the database names in burndown_job.py

Better yet would be to make burndown plugin to survive those unit defitions. Would make upgrading easier.

comment:3 Changed 8 years ago by sambloomquist

  • Priority changed from normal to high
  • Status changed from new to assigned

comment:4 Changed 8 years ago by sambloomquist

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [1268]) Changed database column names in burndown_job.py in order to integrate with the TimingAndEstimationPlugin (http://trac-hacks.org/wiki/TimingAndEstimationPlugin). fixes #498

comment:5 in reply to: ↑ description ; follow-up: Changed 8 years ago by anonymous

  • Resolution fixed deleted
  • Status changed from closed to reopened

Replying to jan@motubo.com:

Nice work...and very interesting. But unfortunately, it is not compatible with the trac-extension http://trac.edgewall.org/wiki/TimeTracking due to different column names in the database. Nothing more i think, so resolving this problem should be easy, does it?

But just the combination of the 2 extensions/hacks would be a really great advantage for us.

comment:6 in reply to: ↑ 5 Changed 8 years ago by sambloomquist

Replying to anonymous:

Replying to jan@motubo.com:

I'm not exactly sure why this ticket was recently re-opened. Is the integration with the TimingAndEstimationPlugin not working for someone?

comment:7 Changed 7 years ago by sambloomquist

  • Resolution set to fixed
  • Status changed from reopened to closed

Closing this ticket again since it shouldn't have been re-opened.

Add Comment

Modify Ticket

Action
as closed .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from sambloomquist. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.