Thanks Harald! As mentioned before, I'd prefer to store the units as hours, and have changed the time_unit field in the time_accounting table to fload(4,2) as per the note in the TODO file. But alas the fractional time unit entered in the interface winds up getting stored as an integer. I think there must be a variable in the code somewhere declared as an integer which is killing the decimal places before they reach the database. I'm having trouble locating it as I'm not a programmer and completely foreign to perl. - Pete McDonnell Manager, Technical Services Hip Interactive
-----Original Message----- From: Harald Paterek [mailto:harald.paterek@moniforce.com] Sent: Friday, February 04, 2005 11:00 AM To: User questions and discussions about OTRS. Subject: Re: [otrs] Time Accounting
I am using this. We are using minutes. But you can use whatever you like. Our time registration package uses 15 minutes as the smallest resolution, so you could use that as your work unit. I am using the time accounting to fill in the time registration at the end of the week. I use this query on the database for that.
select s.login,date_format(t.create_time,'%v-%x'),date_format(t.creat e_time,'%a %d %b %y'), ti.customer_user_id, a.a_subject, t.time_unit, ti.tn, a.a_body from system_user s, time_accounting t, article a, ticket ti where t.create_by=s.id and t.article_id=a.id and t.ticket_id=ti.id and date_format(t.create_time,'%v-%x')='02-2005' ORDER BY s.login, t.create_time
I have not figured out how to build this query into the stats interface so that I can select the week I want to see the time for.
Kind regards,
Harald Paterek
Pete McDonnell wrote:
Is anyone using time accounting in the real world? Someone must... Are you using minutes or hours as the time unit? Any reports or queries that anyone can share for reporting using this data? - Pete McDonnell Manager, Technical Services Hip Interactive
-------------------------------------------------------------- ----------
*From:* Pete McDonnell *Sent:* Thursday, February 03, 2005 10:51 AM *To:* User questions and discussions about OTRS. *Subject:* RE: [otrs] Time Accounting
Correction, both systems are not displaying the same
behaviour. No
fraction of a whole time unit is being stored. The
decimal places
are just zeroes. - Pete McDonnell Manager, Technical Services Hip Interactive
-------------------------------------------------------------- ----------
*From:* Pete McDonnell *Sent:* Thursday, February 03, 2005 10:44 AM *To:* User questions and discussions about OTRS. *Subject:* RE: [otrs] Time Accounting
So I changed the time_accounting.time_unit field to decimal(4,2) and added the following to Kernel/Config.pm: $Self->{FrontendNeedAccountedTime} = 1; $Self->{TimeUnits} = ' (hours)'; The time is only getting recorded as an integer
still though.
IE if I enter 0.25 for the time unit field on a reply 0.00 gets stored in the DB. If I enter 1.25 1.00 gets
stored in the DB.
What else do I need to change? On my live 1.3.1 I
only changed
the time_accounting.time_unit field to decimal(4,2) and it stores the time properly. I did not modify the
Config.pm with
the above two lines on the production server. - Pete McDonnell Manager, Technical Services Hip Interactive
-------------------------------------------------------------- ----------
*From:* Pete McDonnell *Sent:* Tuesday, February 01, 2005 4:13 PM *To:* User questions and discussions about OTRS. *Subject:* [otrs] Time Accounting
I dug up the following from an old 2003 post on
this list.
Just wondering if it'll still work the same on version 1.3.1 and newer versions? Still haven't upgraded the production server to 1.3.2. __SNIP__ /You can set a config option to force time accounting ("$Self->{FrontendNeedAccountedTime} = 1;") and a option to defined the time format name (" $Self->{TimeUnits} = ' (work
units)';") -=>
e. g. "$Self->{TimeUnits} = ' (hours)';"./ __SNIP__
- Pete McDonnell Manager, Technical Services Hip Interactive Phone: (519) 272-0234 x228 /"What the large print giveth, the small print taketh away." - Anonymous/
-------------------------------------------------------------
----------
-
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/
participants (1)
-
Pete McDonnell