[Patch] Record time spent to a custom field (not only for TimingAndEstimationPlugin)

[Octavian Ciubotaru]

It would be nice when you clock off to write time to custom field, as in case of TimingAndEstimationPlugin.

Having this custom fields in trac.ini:

[ticket-custom]
estimatedwork = text
estimatedwork.label = Estimated Work
estimatedwork.order = 1
estimatedwork.value = 0
workdone = text
workdone.label = Work done
workdone.order = 2
workdone.value = 0

To be able to add:

[worklog]
update_field = workdone

[Colin Guthrie]

Sorry, I'm not really sure what you mean here. Worklog does this already.

It integrates with TimingAndEstimationPlugin to do exactly what you say. You have to enable this in the Admin page first tho'.

Or you mean it would be nice to have it log time without TimingAndEstimationPlugin installed?

[Octavian Ciubotaru]

Yes, you're right! I want it to update custom field specified in config, without TimingAndEstimationPlugin installed.

[Colin Guthrie]

OK, that's clearer then :)

I actually use the system inside TimingAndEstimationPlugin to do the cumulative totalling of hours so I'll have to duplicate this same system to achieve this goal.

It's not a bad idea tho', but I've got a couple other fish to fry first, so it wont happen immediately :D

[Octavian Ciubotaru]

Here you can see my modification to allow writing to custom fields. I don't know python, if something is wrong tell me, I'll try to improve me :)

Unfortunately now I can't test it because of this issue:

Traceback (most recent call last):
  File "c:\python25\lib\site-packages\trac-0.11b2-py2.5.egg\trac\web\api.py", line 339, in send_error
    'text/html')
  File "c:\python25\lib\site-packages\trac-0.11b2-py2.5.egg\trac\web\chrome.py", line 672, in render_template
    template = self.load_template(filename, method=method)
  File "c:\python25\lib\site-packages\trac-0.11b2-py2.5.egg\trac\web\chrome.py", line 648, in load_template
    self.templates = TemplateLoader(self.get_all_templates_dirs(),
  File "c:\python25\lib\site-packages\trac-0.11b2-py2.5.egg\trac\web\chrome.py", line 402, in get_all_templates_dirs
    dirs += provider.get_templates_dirs()
  File "build\bdist.win32\egg\worklog\webui.py", line 183, in get_templates_dirs
    from pkg_resources import resource_filename
SystemError: Parent module 'worklog' not loaded

[Colin Guthrie]

Replying to octavian:

Here you can see my modification to allow writing to custom fields. I don't know python, if something is wrong tell me, I'll try to improve me :)

Yeah, unfortunately the "hours" field in TimingAndEstimationPlugin is actually not a real field that is stored. It is intercepted by a ticket change listener in the TimingAndEstimationPlugin and the value in it is combined with the cumulative value (e.g. they are added together) to create a running total.

Your patch will continually update a single field. e.g. if you work for 2 hours and the ticket, stop for a while then go back later and work for 1 hour, the value you want to store is 3 hours but what will actually be stored is 1 hour (e.g. the last value). So there is a litte more work needed :)

Unfortunately now I can't test it because of this issue:

I thought I had fixed that yesterday... are you using the latest svn?

[Octavian Ciubotaru]

Replying to coling:

Replying to octavian:

Here you can see my modification to allow writing to custom fields. I don't know python, if something is wrong tell me, I'll try to improve me :)

Yeah, unfortunately the "hours" field in TimingAndEstimationPlugin is actually not a real field that is stored. It is intercepted by a ticket change listener in the TimingAndEstimationPlugin and the value in it is combined with the cumulative value (e.g. they are added together) to create a running total.

Your patch will continually update a single field. e.g. if you work for 2 hours and the ticket, stop for a while then go back later and work for 1 hour, the value you want to store is 3 hours but what will actually be stored is 1 hour (e.g. the last value). So there is a litte more work needed :)

Thanks, I'll take into account this.

Unfortunately now I can't test it because of this issue:

I thought I had fixed that yesterday... are you using the latest svn?

Yes, rev 3490.

[Octavian Ciubotaru]

I observed strange behavior of trac-admin /project/path upgrade. It does not make any upgrade, just printed Database is up to date, no upgrade necessary..

Maybe WorkLogPlugin does not support sqlite?

[Colin Guthrie]

I test on SQLite so it does support it. No upgrade necessary is the expected behaviour if it's all up-to-date :)

If you inspect a debug log from trac, it should tell you why it can't load worklog. It could be you are not using trac 0.11 trunk. The changes I did yesterday updated things to work with latest trac trunk... I can't remember the exact change but it was one that renamed e.g. TicketAdminPage to TicketAdminPanel (and other similar ones). So you may have to update your Trac. :)

[Octavian Ciubotaru]

Replying to coling:

I test on SQLite so it does support it. No upgrade necessary is the expected behaviour if it's all up-to-date :)

If you inspect a debug log from trac, it should tell you why it can't load worklog. It could be you are not using trac 0.11 trunk. The changes I did yesterday updated things to work with latest trac trunk... I can't remember the exact change but it was one that renamed e.g. TicketAdminPage to TicketAdminPanel (and other similar ones). So you may have to update your Trac. :)

Latest trac solved the problem, upgrade did the job and no more stack traces! Thanks.

Now I can concentrate on the right thing!

[Octavian Ciubotaru]

Updated patch for custom fields update

[Octavian Ciubotaru]

Please see this patch. It works fine for me. I'm not that well at python, so I duplicated some lines of code. Maybe you should confider a little refactoring.

Thanks for the plugin. It is very useful!