Hello
In the time accounting module [on a fresh install] I have set the valid start date as 1st January 2011. When opening the time accounting module to enter test data, the overtime shows -168 hours, if I change the date to Jan 2010 this changes to ZERO.
I cant see any other options to change in the sysconfig settings for time management - any ideas or is this a bug !
thanks
Ian
Time accounting module
Moderator: crythias
Time accounting module
kind regards
Ian
OTRS v3.0.11 ITSM 3.0.5 running on ubuntu 11.10 64bit
with iPhone app
Ian
OTRS v3.0.11 ITSM 3.0.5 running on ubuntu 11.10 64bit
with iPhone app
Re: Time accounting module
Hello Ian,
It is definitively a bug. I created a bug report for it: http://bugs.otrs.org/show_bug.cgi?id=6630
If you want to track it, you can add your email to the Cc list.
Thanks for your help!
Regards,
Elva
It is definitively a bug. I created a bug report for it: http://bugs.otrs.org/show_bug.cgi?id=6630
If you want to track it, you can add your email to the Cc list.
Thanks for your help!
Regards,
Elva
Re: Time accounting module
thanks Elva
I'll add myself onto the list - I hope this is resolved soon as its a key requirement in implementing otrs in our organisation.
regards
Ian
I'll add myself onto the list - I hope this is resolved soon as its a key requirement in implementing otrs in our organisation.
regards
Ian
kind regards
Ian
OTRS v3.0.11 ITSM 3.0.5 running on ubuntu 11.10 64bit
with iPhone app
Ian
OTRS v3.0.11 ITSM 3.0.5 running on ubuntu 11.10 64bit
with iPhone app
Re: Time accounting module
Hello Ian,
It turned out to not be a bug.
For January 2011, the report shows an overtime of -168 hours, if the employee
hasn't entered working hours for this year. These 168 hours are the exact
number of working hours for January, if the default weekly working hours of 40
hours is set.
In other words, the column not only shows the "real" overtime, but also the
working hours this employee has to work this month to fulfill the "target".
Regards,
Elva
It turned out to not be a bug.
For January 2011, the report shows an overtime of -168 hours, if the employee
hasn't entered working hours for this year. These 168 hours are the exact
number of working hours for January, if the default weekly working hours of 40
hours is set.
In other words, the column not only shows the "real" overtime, but also the
working hours this employee has to work this month to fulfill the "target".
Regards,
Elva
Re: Time accounting module
Hi Elva
Thanks for the update. I have to admit I find the reasoning behind this logic strange. Why would I want to see a large minus figure in overtime column, to me it would trigger users to assume they had 168 hrs overtime allowance to use. I presume the same would be if I set default holidays in sysconfig, this column in the time accounting module would show a minus figure until the holiday allowance has been used. In the situation of holidays, I agree showing a countdown of the allowance would be a good option BUT not overtime.
I will change the standard hours to zero and then all hours will show zero unless populated.
To me this is a workaround. I wonder what other users think.
kind regards
Ian
Thanks for the update. I have to admit I find the reasoning behind this logic strange. Why would I want to see a large minus figure in overtime column, to me it would trigger users to assume they had 168 hrs overtime allowance to use. I presume the same would be if I set default holidays in sysconfig, this column in the time accounting module would show a minus figure until the holiday allowance has been used. In the situation of holidays, I agree showing a countdown of the allowance would be a good option BUT not overtime.
I will change the standard hours to zero and then all hours will show zero unless populated.
To me this is a workaround. I wonder what other users think.
kind regards
Ian
kind regards
Ian
OTRS v3.0.11 ITSM 3.0.5 running on ubuntu 11.10 64bit
with iPhone app
Ian
OTRS v3.0.11 ITSM 3.0.5 running on ubuntu 11.10 64bit
with iPhone app