ticket,summary,type,release,owner,status,created,modified,_description,_reporter 10318,Email notification sent even not allowed,defect,0.12,Russ Tyndall,new,2012-09-14T13:27:02+02:00,2021-11-10T01:11:43+01:00,"ver = 1.2.8b With Permissions When [http://trac.edgewall.org/wiki/TracNotification email notification] is configured an email is sent to all CCed people even the changing parameter has limited permission. Eg.'Add Hours to Ticket' field is configured to be visible and may be changed only by users with TRAC_ADMIN permission but notification is sent to all CCed people. ",szuir@… 1780,Create WebAdmin Screen,enhancement,0.10,Russ Tyndall,new,2007-07-12T16:56:20+02:00,2007-07-23T18:38:57+02:00,"Create web-admin page * Allows you to select what reports are available on the management screen * Allows you toggle the completion date field",Russ Tyndall 1853,"Extend the ""Ticket hours per Milestone"" by the milestone's date",enhancement,0.10,Russ Tyndall,new,2007-07-24T12:31:13+02:00,2007-07-24T12:31:13+02:00,"It would be very handy to see the milestones' dates in the report, so you could see if the date is too early or something.",Andy 2082,Feature request for developer activity report grouped milestone,enhancement,0.10,Russ Tyndall,new,2007-10-18T03:42:27+02:00,2007-11-15T20:40:09+01:00,"Hi, The ability to get a developer activity report grouped by milestone would be very helpful. We tend to group different consulting contracts with the same client under their own milestone. Currently, report 11 gives us the developer activity, but it's not possible to see the milestone(s) against which this activity was recorded. My advanced SQL skills are very rusty, and Trac reporting skills non-existent - maybe this is trivial for an expert? Thanks ",jwilliams@… 3998,Stats overview per milestone,enhancement,0.10,Russ Tyndall,new,2008-10-28T11:51:14+01:00,2008-11-13T01:44:55+01:00,"Hi, at http://trac.edgewall.org/attachment/wiki/TimeTracking/time-tracking-milestone.png there is a very nice time stats overview per milestone, so that you get an easy overview on the relation of time estimated and time spent - summed up per milestone. It would be nice to get something like this with the TimingAndEstimationPlugin. Thanks, Achim",Achim.Spangler@… 7359,CommitTicketUpdater integration,enhancement,0.12,Russ Tyndall,new,2010-07-09T14:40:25+02:00,2017-11-18T15:47:36+01:00,"I guess it'd be nice if the (spent x) type markup in commit messges would get through when using the CommitTicketUpdater component, as opposed to the modified trac-post-commit.py",mortee 10250,"RFE: dedicated ""stopwatch"" page",defect,0.11,Russ Tyndall,new,2012-08-09T21:35:54+02:00,2016-08-22T12:16:02+02:00,"First of all, I have to congratulate you on this plugin - it does a lot more than I thought it would and I am very happy. Until now I have been using a free service, slimtimer.com, to manage time sheets and run reports. It is a very good service - mostly AJAX - but it can never be as good as a TRAC plugin in terms of integration with projects. There are, however, a few things SlimTimer.com does exceptionally well, and it would be good if TimingAndEstimation were to duplicate the same functionality. Most notably, slimtimer's dedicated stopwatch (which can be viewed as a popup window, or even fits nicely in an iPhone screen) lists all the currently active Tasks, so that the user can clock time against them. Please support a similar dedicated stopwatch screen, making recording time very easy.",Sam Halliday 10420,SVN commit log analysis in the new post-commit-hook world,enhancement,1.0,Russ Tyndall,new,2012-10-03T15:18:34+02:00,2012-10-10T16:08:42+02:00,"I just love the new trac 1.0, I upgraded from 0.11 but the whole post-commit-hook architecture seems to have been rewritten. I don't have access to this plugin right now but I would like to know if the new hooks are supported, and if so where in the code this is handled? e.g. use start timer on ticket page and then commit with log ""fixes #number"" I'd actually like to be able to have the explicit log functionality working even if the plugin is not installed (say there is a custom field called hours) e.g. fixes #number (27m) where would be the place to look for that?",Sam Halliday 11206,Initialize stopwatch with the value of the text field,enhancement,1.0,Russ Tyndall,new,2013-07-03T09:25:42+02:00,2013-07-04T10:17:43+02:00,"When you press preview, the elapsed time is present in the text field, but the stopwatch resets to zero. If I want to continue working without committing the message, I have to sum the value of the stopwatch with the value from the text field. I tried to do myself a patch because seemed trivial, but couldn't do the part of initialize the stopwatch timer with the value of the field without breaking encapsulation.",xoneca@… 11758,[patch] Encode time with real hour format,enhancement,1.0,Russ Tyndall,new,2014-05-21T20:01:57+02:00,2014-05-21T22:20:59+02:00,"Hi, to avoid brain headache, I have added in my local branch the possibility to encode hour in hour format and not as decimal. By example 1h30, 2h or h45 The encoding as float always works too. I use currently the ""http://trac-hacks.org/svn/timingandestimationplugin/branches/trac0.12-Permissions"" branch. I attach my diff file. I modified ticket.js to always display hour with same format (0h05, in place of 5m). ",Stephan Geulette 13321,"ProgrammingError: relation ""custom_report"" already exists",defect,1.0,Russ Tyndall,new,2017-11-02T13:26:32+01:00,2019-05-06T06:23:44+02:00,"I am relatively new to TRacn and am facing an issue with `TimingAndEstimationPlugin`. This is apparently the same as Ticket [ticket:7446] but I already have the fix applied in my version. I am running `Trac 1.0.9` on `Ubuntu 16.04`. I downloaded this plugin from [https://trac-hacks.org/browser/timingandestimationplugin/branches/trac1.0-Permissions?rev=16948&format=zip here] (`1.5.2b`). My database is `PostgreSQL 9.6.2`. The time field is added to Tikets fine but when I visit `Time Reports`, I get the following error. {{{ ProgrammingError: relation ""custom_report"" already exists File ""/usr/lib/python2.7/dist-packages/trac/web/main.py"", line 554, in _dispatch_request dispatcher.dispatch(req) File ""/usr/lib/python2.7/dist-packages/trac/web/main.py"", line 247, in dispatch resp = chosen_handler.process_request(req) File ""/opt/trac/plugins/timingandestimationplugin-1.5.2b0-py2.7.egg/timingandestimationplugin/webui.py"", line 129, in process_request mgr = CustomReportManager(self.env, self.log) File ""build/bdist.linux-x86_64/egg/timingandestimationplugin/reportmanager.py"", line 22, in __init__ self.upgrade() File ""build/bdist.linux-x86_64/egg/timingandestimationplugin/reportmanager.py"", line 39, in upgrade ""CREATE TABLE custom_report ("" File ""/opt/trac/plugins/timingandestimationplugin-1.5.2b0-py2.7.egg/timingandestimationplugin/dbhelper.py"", line 30, in execute_non_query execute_in_trans(env, (sql, params)) File ""/opt/trac/plugins/timingandestimationplugin-1.5.2b0-py2.7.egg/timingandestimationplugin/dbhelper.py"", line 67, in execute_in_trans raise e }}} I have checked and the table exists in my database. It has the following data. ||id|| uuid ||maingroup|| subgroup|| version|| ||9 ||b24f08c0-d41f-4c63-93a5-25e18a8513c2 ||Timing and Estimation Plugin ||Billing Reports|| 21|| ||10 ||af13564f-0e36-4a17-96c0-632dc68d8d14 ||Timing and Estimation Plugin ||Billing Reports|| 18|| ||11 ||7bd4b0ce-da6d-4b11-8be3-07e65b540d99 ||Timing and Estimation Plugin ||Billing Reports|| 18|| ||12 ||8d785cdb-dcf5-43c9-b2a6-216997b0011a ||Timing and Estimation Plugin ||Ticket/Hour Reports ||17|| ||13 ||71e7c36d-e512-4d0b-b499-087d4d20ff0b ||Timing and Estimation Plugin ||Ticket/Hour Reports|| 17|| ||14 ||5f33b102-e6a6-47e8-976c-ac7a6794a909 ||Timing and Estimation Plugin ||Ticket/Hour Reports ||17|| ||15 ||7816f034-a174-4a94-aed6-358fb648b2fc ||Timing and Estimation Plugin ||Ticket/Hour Reports ||17|| ||16 ||03815803-7688-4f3a-8e65-8d254cc1d1fb ||Timing and Estimation Plugin ||Ticket/Hour Reports ||17|| ||17 ||040c9025-7641-4d18-96ad-2b26b4095566 ||Timing and Estimation Plugin ||Ticket/Hour Reports ||17|| Please guide on how to fix this. Thanks.",Waqas 13405,sum totalhours returns int instead decimal,defect,1.2,Russ Tyndall,new,2018-04-05T17:14:33+02:00,2018-04-09T19:22:28+02:00,"Trac 1.2.2 TimingAndEstimationPlugin 1.5.7b0 MariaDB 10.0.34 If I enter a decimal value for hours like 0.5 the totalhours field is always increased to the next integer value (here 1). The code casts the newvalue with {{{ #!sql CAST( newvalue AS DECIMAL) }}} But if you look to the mysql or mariadb documentation ""DECIMAL"" is used as ""DECIMAL(10,0)"" so the scale is 0 (number of digits after the decimal point). see https://mariadb.com/kb/en/library/decimal/ https://dev.mysql.com/doc/refman/5.5/en/fixed-point-types.html So the cast have to look like {{{ #!sql CAST( newvalue AS DECIMAL(10,2)) }}} I've attached a patch.",Rochi 13558,"""not enough arguments for format string"" during batch ticket update",defect,,Russ Tyndall,new,2019-05-15T20:34:13+02:00,2019-05-15T20:34:13+02:00,"I got this error when trying to do a batch update of tickets, with TimingAndEstimationPlugin 1.6.0b0 installed: {{{ Traceback (most recent call last): File ""c:\python27\lib\site-packages\trac\web\main.py"", line 647, in _dispatch_request dispatcher.dispatch(req) File ""c:\python27\lib\site-packages\trac\web\main.py"", line 248, in dispatch resp = chosen_handler.process_request(req) File ""c:\python27\lib\site-packages\trac\ticket\batch.py"", line 72, in process_request new_values, comment, action) File ""c:\python27\lib\site-packages\trac\ticket\batch.py"", line 210, in _save_ticket_changes t.save_changes(req.authname, comment, when=when) File ""c:\python27\lib\site-packages\trac\ticket\model.py"", line 397, in save_changes listener.ticket_changed(self, comment, author, old_values) File ""c:\python27\lib\site-packages\timingandestimationplugin-1.6.0b0-py2.7.egg\timingandestimationplugin\ticket_daemon.py"", line 157, in ticket_changed self.watch_hours(ticket, author) File ""c:\python27\lib\site-packages\timingandestimationplugin-1.6.0b0-py2.7.egg\timingandestimationplugin\ticket_daemon.py"", line 126, in watch_hours self.log.debug(""deleting ticket change %s %s %s %s"" % tup) TypeError: not enough arguments for format string }}} Looks like the problem is that [source:/timingandestimationplugin/branches/trac1.0-Permissions/timingandestimationplugin/ticket_daemon.py@17107#L125 tup has 3 elements], but the format string expects 4. Removing one of the ""%s""es fixes it.",khym@… 13757,ipnr column in table wiki has been removed with Trac 1.3,defect,,Russ Tyndall,new,2020-02-29T16:27:47+01:00,2020-02-29T16:27:47+01:00,With trac 1.3 the ipnr column from table wiki has been removed. This results in an error when upgrading to Trac 1.3. With the attached patch this is fixed.,anonymous 13933,timingandestimationplugin doesn't work after a 1.2.2 to 1.4.2 trac upgrade,defect,1.4,Russ Tyndall,new,2021-01-07T14:10:10+01:00,2021-01-12T23:25:37+01:00,"After successfully upgrading Trac from 1.2.2 to 1.4.2, I faced some issues regarding a few plugins, particularly with timingandestimationplugin. After {{{trac-admin env/ upgrade}}}, I get stuck in ""Upgrading Database"" step with this error: {{{ 2021-01-07 11:52:55,985 Trac[console] ERROR: Exception in trac-admin command: u'upgrade' Traceback (most recent call last): File ""/usr/local/lib/python2.7/dist-packages/trac/admin/console.py"", line 83, in onecmd rv = cmd.Cmd.onecmd(self, line) or 0 File ""/usr/lib/python2.7/cmd.py"", line 220, in onecmd return self.default(line) File ""/usr/local/lib/python2.7/dist-packages/trac/admin/console.py"", line 252, in default return self.cmd_mgr.execute_command(*args) File ""/usr/local/lib/python2.7/dist-packages/trac/admin/api.py"", line 135, in execute_command return f(*fargs) File ""/usr/local/lib/python2.7/dist-packages/trac/env.py"", line 1062, in _do_upgrade self.env.upgrade(backup=no_backup is None) File ""/usr/local/lib/python2.7/dist-packages/trac/env.py"", line 787, in upgrade participant.upgrade_environment() File ""build/bdist.linux-x86_64/egg/timingandestimationplugin/api.py"", line 247, in upgrade_environment self.do_db_upgrade() File ""build/bdist.linux-x86_64/egg/timingandestimationplugin/api.py"", line 99, in do_db_upgrade dbhelper.set_system_value(self.env, self.db_version_key, self.db_version) File ""build/bdist.linux-x86_64/egg/timingandestimationplugin/dbhelper.py"", line 147, in set_system_value value, key) File ""build/bdist.linux-x86_64/egg/timingandestimationplugin/dbhelper.py"", line 46, in execute_non_query execute_in_trans(env, (sql, params)) File ""build/bdist.linux-x86_64/egg/timingandestimationplugin/dbhelper.py"", line 83, in execute_in_trans raise e ProgrammingError: (1064, u""You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'system (value, name) VALUES (6, 'TimingAndEstimationPlugin_Db_Version')' at line 1"") }}} I tried upgrading the plugin from 1.3.7b0 (which worked correctly with Trac 1.2.2) to 1.6.0 and added a few hacks found in this ticket https://trac-hacks.org/ticket/13732, but the problem still persists. Any idea why? My configuration: {{{ User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0 Trac 1.4.2 Babel 2.6.0 Docutils 0.16 Genshi 0.7.3 (with speedups) GIT 2.25.1 Jinja2 2.10.3 mod_wsgi 4.6.8 (WSGIProcessGroup voxygen WSGIApplicationGroup %{GLOBAL}) MySQL server: ""8.0.22-0ubuntu0.20.04.3"", client: ""0.10.1"", thread-safe: True Pygments 2.3.1 pymysql 0.10.1 Python 2.7.18 (default, Aug 4 2020, 11:16:42) [GCC 9.3.0] pytz 2019.3 setuptools 44.1.1 Subversion 1.13.0 (r1867053) jQuery 1.12.4 jQuery UI 1.12.1 jQuery Timepicker 1.6.3 }}}",guillaume22 1731,Biling and other reports do not reflect a retargeted ticket,enhancement,0.10,Russ Tyndall,new,2007-07-04T14:59:22+02:00,2007-08-27T16:21:33+02:00,"Not sure if this is possible but, currently when a ticket is retargeted to another milestone the plugin reports on the total hours associated with the ticket. It would be nice if you could view hours for a given milestone if a ticket spans multiple milestones. I have logged a related bug against trac which deals with the fact that re targeting does not get reflected in a tickets change history: http://trac.edgewall.org/ticket/5658#preview",mlists@… 2464,Log time for previous days or other people,enhancement,0.10,Russ Tyndall,new,2008-01-23T10:37:53+01:00,2008-05-22T15:39:39+02:00,"When you work on a ticket, sometime you forget to log time. So, in order to have correct dates on work logs, it would be nice to add capability : * for a developer to log time for previous days * for an admin to log time for previous days and for other people ",jmdelehaye@… 13732,Enable TimingAndEstimationPlugin on Trac 1.4 - actually not a question,enhancement,1.4,Ryan J Ollos,accepted,2020-01-17T21:50:14+01:00,2023-07-17T16:21:27+02:00,"I have tried to install almost all of the plugins for time tracking... but I am only interested on TimingAnEstimationPlugin, so i would like to make it run. Luckily I could. Latest updates on trac-hacks seem this plugin not to be maintaned so far. I could make it run too simple, as I am not fluent on Python. === Errors if you follow current installation steps: - Trac[loader] ERROR: Skipping ""timingandestimationplugin = timingandestimationplugin"": ImportError: No module named genshi.core - OperationalError: table wiki has no column named ipnr === Steps to have it running (for as an ignorant as me): First error can be fixed installing genshi - >pip install genshi Second error can be fixed modifying lines 196 and 197 of **./timingandestimationplugin/api.py** - **196** remove 'ipnr,' - **197** remove '127.0.0.1,' 0. install genshi **pip install genshi** 1. download [export:timingandestimationplugin/branches/trac1.0 Zipped source for plugin for Trac 1.0] (it is the same link as on plugin's wiki) 2. unzip on a folder an move to that folder 3. Modify **./timingandestimationplugin/api.py** 4. build the source **python setup.py build** 5. install the source **python setup.py install** 6. upgrade track **trac-admin YOUR_TRAC_PROJECT upgrade** 7. upgrade wiki **trac-admin YOUR_TRAC_PROJECT wiki upgrade** ---- Please, note that this is a quick&dirty turnaround, not **THE** solution.",a.gm@…