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

[jan@…]

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.

[Sam Bloomquist]

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.

[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.

[Sam Bloomquist]

(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

[anonymous]

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.

[Sam Bloomquist]

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?

[Sam Bloomquist]

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