Subscribe: Trac Hacks - Plugins Macros etc.: {9} Active Hack Tickets
Added By: Feedage Forager Feedage Grade A rated
Language: English
build bdist  file  line  linux egg  log  plugin  python  stop work  stop  ticket  time  trac  work log  work  worklog 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Trac Hacks - Plugins Macros etc.: {9} Active Hack Tickets

Trac Hacks - Plugins Macros etc.: {9} Active Tickets for WorkLogPlugin

Trac Report - * List active tickets for WorkLogPlugin by priority. * Color each row based on priority. * If a ticket has been accepted, a '*' is appended after the owner's name


#1667: Create a desktop app to record time spend on a given task and update ticket when done

Fri, 15 Jun 2007 08:32:38 GMTThu, 12 Jan 2017 21:00:46 GMT

This plugin would be make a lot more useful by creating a desktop application (python-gtk? or for OSX or it's clone Vista, as a Widget or Gadget).

This would simply allow starting and stopping work on a given task and the time spend therein recorded locally. Little warnings would flash up periodically (e.g. every 15 minutes - configurable) to remind the user they are still working on this ticket - I get easily distracted ;)

Once the user clicks "stop", they will be asked if they want to submit now, and if so they have to enter in a brief description of what they have done. If they choose not to, the time will be cached locally until a later date.

This will make use of the XMLRPC interface and as such may need changes to the plugin itself (I am unsure of the technical details here).

I will start work on this in the near(ish) future as I think this kind of recording app would be of great benefit in our company.

My goal is for a cross platform tool as we have people running Linux, OSX and Windows in my organisation. It would need to support HTTP level authentication of the XMLRPC side of things.

Comments/suggestions welcome.

It may come in the form of a Qt App as I need to learn more about that and I'm quite happy in C++ but any other implementation suggestions are welcome (e.g. if python-gtk is a good option I'd like to look into it - Not got any epxerience of running such apps on Windows or OSX tho').


#1898: [Patch] Some suggested changes to worklogplugin

Tue, 07 Aug 2007 04:15:30 GMTThu, 12 Jan 2017 21:00:46 GMT

Awesome plugin - this one should definitely be added to the main trac once it's mature.

I've made some changes to the worklog plugin that you might find useful:

  • Added a comment field to work logs
  • Changed the "Start Work" & "Stop Work" button actions to return to the originating ticket.
  • Changed the main worklog page to list all the worklog entries, instead of just showing your most recent log. This is handy for importing into Excel (for example), where all sorts of interesting reporting with pretty graphs can be done. This cold be put somewhere else, but I'm not yet sure where...
  • Corrected a few (incorrect) references to "Timing and Estimation Plugin."
  • Changed some of the css styling to better fit worklog entries on the page.

It's all pretty simple stuff but I'm just a beginner in python so my apologies for any errors. It all works for me. :)

Please find a diff attached.

#1935: Integration with Teamtrac

Wed, 15 Aug 2007 13:30:28 GMTThu, 12 Jan 2017 21:00:46 GMT

I was looking at and thinking what a good fit your tool would be, if used with them. Actually I'm not sure if it would be better to integrate WorkLogPlugin with them or the TimingAndEstimationPlugin. Let me know your thoughts I've done php work so I don't mind doing some integration if, you have any implementation ideas.

#1943: Alloww several users to work on the same ticket. & 1 user on more than one ticket

Sat, 18 Aug 2007 19:28:18 GMTThu, 12 Jan 2017 21:00:46 GMT

Hi coling:

First of all, congratulations for this nice plugin. I'm using it to manage the projects of my team and we found it very useful.

We are making some modifications (actually I'm are testing them already) in order to allow more than one user to work on the same ticket. We do a lot of pair programming so it's quite common to have two members of our team spending time on the same tasks.

What we are doing is using a ticket custom field (worklogusers) which contains a comma separated list of users which are allowed to work on a ticket. Users listed here can start and stop work on the ticket. This option can be activated/deactivated using a new worklog option called multipleusers.

I don't have all the time I would like to code this, but I hope next week I can submit a patch with the new functionality. We have used revision r2571 as starting point.



#2107: Integration with Workflow

Thu, 25 Oct 2007 17:19:13 GMTThu, 12 Jan 2017 21:00:46 GMT

Hi coling,

Can you explain please your plugin can work with .11 workflows ? i.e. If you start working the ticket status goes to the in_work status if you stop work to the assigned status (in the enterprsie workflow example)

Thanks a lot,


#2426: suppress start and commentless stop notifications

Wed, 16 Jan 2008 13:10:17 GMTThu, 12 Jan 2017 21:00:46 GMT

It would be useful to be able to prevent Trac from sending notifications by e-mail when someone is starting to work on a ticket or stopping with no comment.

I like to keep people informed with Trac's notification mechanism, but Work Log causes their inbox to be flooded when I'm working on a ticket in multiple sessions.

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

Tue, 08 Apr 2008 19:59:39 GMTThu, 12 Jan 2017 21:00:46 GMT

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:

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:

update_field = workdone

#2883: WorkLog header for ticket dissapears if I play with time on client machine

Wed, 09 Apr 2008 14:25:05 GMTThu, 12 Jan 2017 21:00:46 GMT

I was testing how the plugin works and found that when I change the time (+1 hour) on my machine and do Stop Work it counts 1 hour and everything is ok.

But when I switch time back (-1 hour) and start to work instead of [Stop Work] button in header I see nothing. So I can't stop timing. Even after one hour.

This is kinda cheating :) But I think this case should be treated anyway. At least to be able to stop timing for those issues.

#2903: Allow time to be recorded in different custom fields depending on workflow state

Mon, 14 Apr 2008 00:57:22 GMTThu, 12 Jan 2017 21:00:46 GMT

We use 'enterprise' workflow in Trac, and need to track development and testing times separately. This could be done if worklog plugin could be set up to record time into different custom fields depending on the workflow state... something like

customfield.in_qa=testing_time customfield.*=dev_time

or something like that...

#2935: Error with german "Umlaute", example ä, ü etc.

Sun, 20 Apr 2008 13:34:18 GMTThu, 12 Jan 2017 21:00:46 GMT

If I try to comment a worklog with special characters, for example "ä" I get the following error:

Traceback (most recent call last):
  File "/var/lib/python-support/python2.4/trac/web/", line 387, in dispatch_request
  File "/var/lib/python-support/python2.4/trac/web/", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "build/bdist.linux-i686/egg/worklog/", line 123, in process_request
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 0: ordinal not in range(128)

In german we have these charecters very often and it would be nice, if we don´t have to circumscribe our comments.

#3089: "Stop Work" behavior not compatible with IE7 & FF3

Wed, 28 May 2008 08:46:05 GMTThu, 12 Jan 2017 21:00:46 GMT


I really like your Trac plugin. I'm currently exploring using it for time tracking for my Java development team.

In WorkLogPlugin 0.10 the "Stop Work" behavior was much simpler (a text field) however due to a div positioning issue the box was overlapping the navigation bar in IE7.

In WorkLogPlugin 0.11 I notice you added a fancy effect where the screen goes dark and you can enter a comment and choose the date/time you stopped work. This also has issues in IE7 (you can't enter anything in the text field). Also, the textarea overlaps the edge of the box.

This makes it impossible to use the Stop Work button in IE7 which significantly hampers the usability of the plugin.

Would it be possible to have an admin option to choose which style of Stop Work comments is used (if any)?

Personally I much prefer the 0.10 implementation (much simpler). If the div positioning issue could be resolved I would say it perfectly meets our needs.

I'm not a big fan of the screen-dimming effect in 0.11 and if I could disable I would.

I think subtlety works best here. Think of the idea of timer - you click to turn it on, and click again to turn it off. Having a dialog box pop up is a bit counter-intuitive.

Other than that, I would maybe suggest that the "Record Time via Time and Estimation" option be enabled by default.

Keep up the good work!


#4126: Harvest Timer API Intergration

Thu, 20 Nov 2008 00:16:39 GMTThu, 12 Jan 2017 21:00:46 GMT

Our company is interested in enhancing a timer plugin for Trac to update time in the Harvest Time Tacking Service so that developers can start and stop their timers in trac and update their Harvest time sheet via the Harvest API ( automatically.

We are planning to do this ourselves (or subcontract it out if a trac developer wants to do it) but would like input on the design so that it is useful to other trac users. We would also prefer to enhance the existing worklog plugin to help others who might want this feature and to save ourselves some coding time. Any feedback is greatly appreciated!

#4247: Plugin doesn't seem to take into account Trac timezone settings

Wed, 10 Dec 2008 18:04:43 GMTThu, 12 Jan 2017 21:00:46 GMT

Not sure if anyone is still working on this but. I'm using Trac 0.11 The server that trac is running on is in the US however we are in the UK The Timing and Estimation Plugin correctly displayes its times in its reports The Times in the WorkLogPlugin all look as if they are using a us timezone

#4712: Duplicating records for hours worked on a user in ticket_change table

Fri, 27 Feb 2009 12:23:06 GMTThu, 12 Jan 2017 21:00:46 GMT


We have installed these modules:


We noticed that there is a problem with duplicating records for work hours per user in table ticket_change in postgresql database. The problem is reproducing this way:

Go to a ticket and press: Start work.

Then without stopping the work, we just change resolution to something (for example Fixed) and apply changes. Then work is stopping and ticket is closing. After then in database i see 2 records for hours.

Like these:

13  1235734626  anebi	hours	0.0	2.81
13  1235734625  anebi	comment	4	anebi worked on this ticket for 2 hours, 48 minut...
13  1235734625  anebi	hours	0	2.81
13  1235734626	anebi	comment	3	 - Made some tests with PHPFileNavigator.

You see the hours field and value. They are the same. Only different is timestamp. This happens because worklog is recrded this 1 second before the other record.

Maybe this is problem with timingandestimationplugin plugin. I'm nut sure.

#4850: Problems with active and inactive "Stop" button in stop work window.

Sun, 29 Mar 2009 16:57:43 GMTThu, 12 Jan 2017 21:00:46 GMT

Hi, we have installed these components:

trac- worklogplugin-r5364 timingandestimationplugin_branches_trac0.11-r5364

The situation is this:

  • I have started the work log on a ticket. I go to the ticket and click on "Stop" button. Then the window for stopping the work is loading. There "Stop" button is active. I can stop the work.
  • If i click on "close" link then the window is closing. when i click again on "Stop Work", then the window for stopping the work is loading and "Stop" button is inactive. I cannot stop the work.
  • I click "close" link again, and then refresh the page on the browser and click again on "Stop Work", the windows is loading and "Stop" button is active. But when i click on "Stop", the work is not stopping.
  • I need to go to somewhere else on trac and then go back to the ticket. Then i click stop work and "stop". Then everything works fine, it stop the work.

What is expecting:

  • When i go to a ticket anc click "Stop work", then "Stop", work to stop.
  • If i click on "close" link on stop work window and again to "Stop Work', the "stop" button to be active and to able to stop the work.
  • After page refresh to be able to stop work, not only button to be active.

I don't know if is a real bug or is a problem with my installation, but we have this problem.

Best regards!

#5777: Add an ExtensionPoint

Fri, 04 Sep 2009 10:47:25 GMTThu, 12 Jan 2017 21:00:46 GMT

Hello, great plug-in!

But right now I'm developing some new plugin and I was very disappointed in one thing - other plug-ins can't find the way to handle/find out/etc. event of starting/stopping work on ticket. Yes this could may made by listening of ticket_change of ITicketChangeListener, but it is not the same as if it would be WorkLogPlugin event.

So, I was added couple of classes to add new ExtensionPoint and make WorkLogManager be able call listeners on starting/stopping work on ticket.

PS: sorry for my bad English =) and sorry I'm python and Trac noob, may be I'm doing things in wrong direction, but as for my self I'm going to use this ExtensionPoint in my trac instances

#7786: [Patch] Discriminating excessive work hours.

Thu, 07 Oct 2010 07:34:40 GMTThu, 12 Jan 2017 21:00:46 GMT

When using worklog plugin, if a user forgets to stop his/her clock when work ended, he has given a chance (to correct time on a popup window) to do it. If he even misses this chance, work log records some excessive working hours. Even we can't prevent it from happening, with this patch, we have a chance to discriminate such logs on user view for work log. On Work log for User view, if work is not stopped on the day it started, it will be colorized. If this condition is met and work continues, it will be highlighted with yellow color. Otherwise it will be highlighted in light red color.

Patch applies to [6472] and 0.11 branch of worklog plugin.

#7910: Problem Worklog_Stop with information date/time

Tue, 26 Oct 2010 17:47:12 GMTThu, 12 Jan 2017 21:00:46 GMT

I have installed the plugin in the latest version and are having problems because of time zone.

This month we had changed to standard time +1 hour and now I can't stop the ticket retroactively because the schedule is lost.

I could not find what information the file change because of JQuery has been customized.

Look the picture.

#8405: Document permissions and some possible improvements

Mon, 17 Jan 2011 23:19:20 GMTThu, 12 Jan 2017 21:00:46 GMT

  • The WORK_VIEW, WORK_LOG, and WORK_ADMIN permissions should be documented on the project's wiki page.
  • If the WORK_LOG permissions does what I think it does, we might rename it to WORK_EDIT, to be more consistent with the permission naming scheme in Trac.
  • I've granted WORK_LOG permission to a user, but that user can't start work on a ticket and sees the message WORK_VIEW privileges are required to perform this operation. To be more consistent with Trac implementation of permissions, WORK_LOG (WORK_EDIT) should grant all permissions granted by WORK_VIEW. In the same way, WORK_ADMIN should grant all permissions granted by WORK_LOG (WORK_EDIT).

#8416: It should not be possible to start work on a closed ticket

Tue, 18 Jan 2011 22:39:12 GMTThu, 12 Jan 2017 21:00:46 GMT

Perhaps the start work button or entire template stream modification can be removed for closed tickets.

#8508: Installation fails with PostgreSQL database backend

Wed, 16 Feb 2011 03:50:25 GMTThu, 12 Jan 2017 21:00:46 GMT

I installed WorkLogPlugin using easy_install, edited my trac.ini to include:

worklog.* = enabled
timingandestimation = true

I then ran:

trac-admin /var/trac upgrade

And it failed with:

Worklog needs an upgrade
 * Upgrading Database
Creating work_log table
InternalError: current transaction is aborted, commands ignored until end of transaction block

I examined the code in and traced the problem to the following section:

    def do_db_upgrade(self, db):
        # Legacy support hack (supports upgrades from revisions r2495 or before)
        if self.db_installed_version == 0:
                cursor = self.env.get_read_db().cursor()
                cursor.execute('SELECT * FROM work_log LIMIT 1')
                # We've succeeded so we actually have version 1
                self.db_installed_version = 1
                self.db_installed_version = 0

What I believe is happening is the SELECT command fails with an error. In PostgreSQL, this invalidates the transaction until a rollback is performed. There is no rollback in the code, so when the function later tries to create a table, the InternalError is generated.

I was able to work around the problem by commenting out the SELECT test and simply setting db_installed_version to zero (which works because this is a fresh install), but I don't know the whole installation workflow well enough to suggest a permanent fix. My guess is that rolling back the transaction is bad because it might undo changes done by other plugins installed at the same time. I think that you probably need to use an alternate method of determining if the table exists or not.

#8762: Time not appearing in stop work pop up

Wed, 04 May 2011 11:18:07 GMTThu, 12 Jan 2017 21:00:46 GMT

I seem to have an issue in that when I click stopwork on a ticket I get an error message and the time doesn't appear below the calendar (screen cap attached). If I press ok on the error and click stop work then the time is recorded as it should be.

The error message varies depending on the browser: FireFox: TypeError: $.timeEntry is undefined Chrome: TypeError: Cannot read property '_defaults' of undefined IE: TypeError: $.timeEntry._defaults is null or not an object

I don't know whether there's a problem with my trac install or what but it is rather annoying.

#9500: deleting tickets leaves work_log table entries pointing to nonexistant ticket

Thu, 27 Oct 2011 06:31:18 GMTThu, 12 Jan 2017 21:00:46 GMT

If you use Trac's built in 'delete ticket' plugin, relevant items from the 'ticket' and 'ticket_changes' table are deleted, but not from the 'work_log' table.

#9664: Support for agilo tickets

Thu, 05 Jan 2012 12:30:19 GMTThu, 12 Jan 2017 21:00:46 GMT

Agilo for Trac defines its own ticket system (while disabling built in ticket API), and when trying to start/stop work for an Agilo ticket, I get AttributeError: 'Ticket' object has no attribute 'is_writeable_field'

I think this is similar to

So, what can be done to fix this cleanly, rather than using Agilo ticket objects?

#9752: Should be upgraded to jQuery UI 1.8.16 so that it doesn't conflict with DateFieldPlugin

Thu, 02 Feb 2012 07:46:44 GMTThu, 12 Jan 2017 21:00:46 GMT

As original discussed in #9567.

#10014: When SubTicketsPlugin module is enabled it crashes the CSS & JS

Wed, 09 May 2012 13:42:34 GMTThu, 12 Jan 2017 21:00:46 GMT

Trac 0.12.3 on Windows Xp Pro Sp3 Apache 2.2.21 MySQL 5.5.0-m2-community Python 2.6.2 Subversion 1.7.1

I've installed the WorkLogPlugin and it worked perfectly... When I added the SubticketsPlugin to my Trac it crashes the WorkLogPlugin CSS and JS...

I've attached the screenshots when:

  1. SubticketsPlugin 0.1.0 has enabled only SubticketsPlugin and worklog 0.2 is enabled
    • Work Log Summary looks OK,
    • Ticket View looks OK,
  2. SubticketsPlugin 0.1.0 and worklog 0.2 are enabled
    • Work Log Summary looks bad,
    • Ticket View looks bad,

#10132: Implementation with TracHoursPlugin

Tue, 03 Jul 2012 19:11:51 GMTThu, 12 Jan 2017 21:00:46 GMT

Althrough TracHoursPlugin should be supported, tracked time was not stored to its database table. I'm not used to work in Python, so my patch is not done the best, however I fixed it for myself by slight modification of In stop_work procedure there is section used to store time in TimingAndEstimationPlugin, I added code for TracHoursPlugin there also:

    if plugtne:
        tckt['hours'] = hours
    if plughrs:
        trachours = TracHoursPlugin(self.env)
        trachours.add_ticket_hours(active['ticket'], self.authname, delta * 60)
    self.save_ticket(tckt, message)
    message = ''

Of course, also

from trachours.hours import TracHoursPlugin

should be added, however this implies dependency on Plugin not installed by all users. Because I do not know Python, I do not know proper way of dealing with it.

Either way, thanks for the Plugin!

#10206: Duplicate column name "comment"

Sun, 29 Jul 2012 23:59:38 GMTFri, 14 Jun 2013 10:42:53 GMT

After I installed your plugin at the system level, and enabled it for one of my projects, I get an error from trac upon looking at any trac page linked to that project:

TracError: OperationalError: duplicate column name: comment

Editing trac.ini to remove the worklog plugin enable statements fixes the project. Other enabled plugins are:

autoupgrade.autoupgrade.autoupgrade = enabled
batchmod.web_ui.batchmodifymodule = enabled
childtickets.admin.childticketsadminpanel = enabled
childtickets.childtickets.tracchildticketsmodule = enabled
coderev.api.codereviewersystem = enabled
coderev.web_ui.changesetticketmapper = enabled
coderev.web_ui.codereviewermodule = enabled
coderev.web_ui.committicketreferencemacro = enabled
mastertickets.api.masterticketssystem = enabled
mastertickets.web_ui.masterticketsmodule = enabled
simplemultiproject.admin.smpadminpanel = enabled
simplemultiproject.admin_component.smpcomponentadminpanel = enabled
simplemultiproject.environmentsetup.smpenvironmentsetupparticipant = enabled
simplemultiproject.milestone.smpmilestoneproject = enabled
simplemultiproject.model.smpmodel = enabled
simplemultiproject.roadmap.smproadmapproject = enabled
simplemultiproject.roadmap.smproadmapprojectfilter = enabled
simplemultiproject.ticket.smpticketproject = enabled
simplemultiproject.timeline.smptimelineprojectfilter = enabled
simplemultiproject.version.smpversionproject = enabled
tracbzr.backend.bzrconnector = enabled
tracbzr.backend.bzrpropertyrenderer = enabled
tracbzr.backend.bzrwikimacros = enabled
tracopt.ticket.deleter.ticketdeleter = enabled
tracrpc.api.xmlrpcsystem = enabled
tracrpc.json_rpc.jsonrpcprotocol = enabled = enabled
tracrpc.ticket.componentrpc = enabled
tracrpc.ticket.milestonerpc = enabled
tracrpc.ticket.priorityrpc = enabled
tracrpc.ticket.resolutionrpc = enabled
tracrpc.ticket.severityrpc = enabled
tracrpc.ticket.statusrpc = enabled
tracrpc.ticket.ticketrpc = enabled
tracrpc.ticket.typerpc = enabled
tracrpc.ticket.versionrpc = enabled
tracrpc.web_ui.rpcweb = enabled = enabled
tracrpc.xml_rpc.xmlrpcprotocol = enabled
whiteboard.web_ui.whiteboardmodule = enabled

#10259: not just for Owner of issue

Fri, 10 Aug 2012 12:52:54 GMTThu, 12 Jan 2017 21:00:46 GMT

I am using SVN version 10794 so that it works with 0.11.7.

In a pair programming situation, I need to clock time against two developers - but TRAC only allows one Owner and WorkLogPlugin only allows the Owner to clock time. Can you perhaps use the CC field or just leave it open?

#10261: Delete, edit and create work logs

Fri, 10 Aug 2012 14:37:43 GMTThu, 12 Jan 2017 21:00:46 GMT

It does not appear to be possible to delete, edit or create work logs. It would be very useful to be able to do this. Consider the use case where the developer simply forgets to start the timer, or set it running by accident. It would be useful to be able to provide a way to log all this information without having to use the timer.

#10265: Slimtimer-like functionality

Fri, 10 Aug 2012 14:48:00 GMTThu, 12 Jan 2017 21:00:46 GMT

I recorded similar comments against TimingAndEstimation but I'm keen to hear what you have to say about it.

I see TimingAndEstimation as the function at the top of the time management stack, which produces reports of time spent on issues. It doesn't really have the ability to print out reports for individuals, or to show that kind of breakdown for an issue. It essentially doesn't provide a way to record and report time sheets - which makes it a non-starter for billing except for completely homogeneous teams where each person works alone.

However, I'm not convinced about WorkLogPlugin as the solution to my requirements. It has obviously been developed with different goals that what I would like to achieve. For example, it enforces that only the Owner can log time against an issue <>, and it is not very easy to use when compared to external services such as It is also not possible to delete, edit, or create logs without using the timer.

For me to be able to use a time tracking system inside TRAC it would absolutely have to meet these criteria:

  1. allow any registered user to clock time against any OPEN issue (not just the owner)
  1. have a dedicated stopwatch page/popup that has a similar UI to slimtimer. This would list Owned issues and those on which you are CCd, plus a search to bring up anything from the issue tracker.
  1. produce timesheet reports, with similar options as slimtimer.
  1. record the date and value for estimates, given by individual users. The average could be saved as the issue's actual estimate.

I think, ultimately, any tool that does this would have to update the data stored in the fields stored by TimingAndEstimation so that plugins which use the estimate/hours columns would have access to these fields. Perhaps what I am wanting is new plugin, that I might have to write myself.

Basically, I would like to have all the recording/reporting of slimtimer right in TRAC :-) (The slimtimer plugin doesn't work for 0.11+ and only synchronises with slimtimer anyway)

If you don't want to work on this, please feel free to CLOSE. But I'd appreciate as much advice as you can to help me out, should I decide to write a plugin.

#10646: Only works with default ticket workflow

Thu, 22 Nov 2012 01:43:11 GMTThu, 12 Jan 2017 21:00:46 GMT

For example, using a workflow I derived from is incompatible with this plugin, which is a shame. Some of the problems include the plugin putting tickets in non-existent statuses (such as 'accepted').

While I modified and so that it works with the given workflow (see attachments), this shouldn't be hardcoded but should be read from ticket.ini

I suggest at least specifying in trac.ini the names of the statuses that the plugin checks for and assigns. The next step to make it fully compatible would then be to respect the specified transitions in [ticket-workflow], including permissions.

#11196: Add ability to log work time explicitly without using timer

Wed, 26 Jun 2013 09:29:28 GMTSun, 16 Apr 2017 08:23:22 GMT

This plugin provides most all of the functionality we are seeking, however, the "timer" (start|stop work) method of logging time is to restrictive for our needs. We often jump between multiple tickets at a time, and going in to each ticket to click start each time we switch between them is more of a hindrance than it is worth. This also causes issues since we bill per .5hr, and when switching between tickets frequently, the compounding of rounded time can result in a much higher or much lower recorded time than was actually worked.

I would like to request that an option to "Log time" is added. A dialog in which you can simply specify the duration that you worked on the ticket rather than having to use the clock timer.

#11459: OperationalError: (1054, "Unknown column 'hours' in 'field list'")

Fri, 27 Dec 2013 05:17:29 GMTThu, 12 Jan 2017 21:00:46 GMT

How to Reproduce While doing a POST operation on /worklog, Trac issued an internal error. (please provide additional details here) Request parameters: {'__FORM_TOKEN': u'c28fc3ec7a28b6b4baf3f85d', 'comment': u'Test ', 'source_url': u'/trac/ticket/68', 'stoptime': u'', 'stopwork': u'Stop Work', 'ticket': u'68'} User agent: Mozilla/5.0 (Windows NT 5.1; rv:26.0) Gecko/20100101 Firefox/26.0 System Information Trac 1.0.1 Agilo 0.9.12 Genshi 0.7 (with speedups) GIT GIT MySQL server: "5.5.34-0ubuntu0.12.04.1", client: "5.5.34", thread-safe: 1 MySQLdb 1.2.4 Pygments 1.4 Python 2.7.3 (default, Sep 26 2013, 20:03:06) [GCC 4.6.3] pytz 2011k setuptools 2.0.1 jQuery 1.7.2 Enabled Plugins agilo 0.9.12 AutocompleteUsers 0.4.2dev-r12687 ComponentDependencyPlugin 0.1 timingandestimationplugin 1.3.7 TracAccountManager 0.4.3 TracAutoComplete 0.1 TracGit TracTicketChangesets 1.0dev-r10004 worklog 0.3dev-r12358 Python Traceback Traceback (most recent call last): File "build/bdist.linux-x86_64/egg/trac/web/", line 497, in _dispatch_request dispatcher.dispatch(req) File "build/bdist.linux-x86_64/egg/trac/web/", line 214, in dispatch resp = chosen_handler.process_request(req) File "build/bdist.linux-x86_64/egg/worklog/", line 143, in process_request if not mgr.stop_work(stoptime, comment): File "build/bdist.linux-x86_64/egg/worklog/", line 224, in stop_work self.save_ticket(tckt, message) File "build/bdist.linux-x86_64/egg/worklog/", line 81, in save_ticket tckt.save_changes(self.authname, msg, nowdt, cnum=str(cnum+1)) File "/usr/local/lib/python2.7/dist-packages/agilo-0.9.12-py2.7.egg/agilo/ticket/", line 860, in save_changes res = super(AgiloTicket, self).save_changes(author, comment, when, db, cnum, replyto=replyto) File "build/bdist.linux-x86_64/egg/trac/ticket/", line 346, in save_changes % name, (self[name], File "build/bdist.linux-x86_64/egg/trac/db/", line 121, in execute cursor.execute(query, params) File "build/bdist.linux-x86_64/egg/trac/db/", line 65, in execute return self.cursor.execute(sql_escape_percent(sql), args) File "/usr/local/lib/python2.7/dist-packages/MySQL_python-1.2.4-py2.7-linux-x86_64.egg/MySQLdb/", line 201, in execute self.errorhandler(self, exc, value) File "/usr/local/lib/python2.7/dist-packages/MySQL_python-1.2.4-py2.7-linux-x86_64.egg/MySQLdb/", line 36, in defaulterrorhandler raise errorclass, errorvalue OperationalError: (1054, "Unknown column 'hours' in 'field list'") [...]

#11669: MySQL to PostgreSQL migration fails with worklog usermanual

Wed, 02 Apr 2014 20:14:06 GMTThu, 12 Jan 2017 21:00:46 GMT

This is a great plugin that we use to slave-drive oversee our devs. Unfortunately, it seems it can't be migrated with the TracMigratePlugin:

./ --in-place /srv/trac postgres://tracuser:nalkyergatte@

Worklog needs an upgrade
 * Upgrading Database
Creating work_log table
Updating work_log table (v2)
Updating work_log table (v3)
 * Upgrading usermanual
Traceback (most recent call last):
  File "./", line 55, in 
    sys.exit(main(sys.argv[1:]) or 0)
  File "./", line 51, in main
    return TracMigrationCommand(env)._do_migrate(dest, dburi)
  File "/tmp/m/tracmigrate/", line 29, in _do_migrate
    return self._do_migrate_inplace(dburi)
  File "/tmp/m/tracmigrate/", line 60, in _do_migrate_inplace
    env = self._create_env(env_path, dburi)
  File "/tmp/m/tracmigrate/", line 92, in _create_env
    env = Environment(env_path, create=True, options=options)
  File "/usr/lib/python2.7/site-packages/trac/", line 124, in __call__
    self.__init__(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/trac/", line 288, in __init__
  File "build/bdist.linux-x86_64/egg/worklog/", line 55, in environment_created
  File "build/bdist.linux-x86_64/egg/worklog/", line 182, in upgrade_environment
  File "build/bdist.linux-x86_64/egg/worklog/", line 146, in do_user_man_update
AttributeError: 'NoneType' object has no attribute 'cursor'