Re: [Tsheetx-developers] Working, Time Off, Absences, etc

[paul c. <pdc...@bl...>]

ive had to do something similar -   different rates for working before 
and after 7pm.
I just let my users enter start and finish times and  when i analysed 
the data I split it at 7pm.

I found it easier in perl using Date::Manip  and the various methods  
for comparing times .
(I'm  not really PHP programmer)

Happy to share the code if it helps


Hi,
>    
>> yes, that's interesting, but we have to be able to document not only the paid hours but the actual times. e. g. 9:00 - 17:00 work time, 17:00-18:00 overtime, 19:00-21:30 travel time...
>>      
> I think that overtime is more based on a calculation (after 8 hours of
> work, for example it's overtime (but I think it must be done on a week
> basis not day basis)).
>
> For travel it's a task in the different projects (or in one project if
> you don't bill the client for it).
>
> Can I please ask you, Khrabina, to send an example of a report that you
> must have so we can see necessary informations that need to be on it?
>
> What I would propose regarding this conversation is :
>
> Having one field where you have the type of "work" tasks, "Paid time
> off" and "unpaid time off" like Scott Miller propose it.
>
> Having fields on the proprieties page where we can define normal work
> hours (for example 8h00 - 20h00) and the price factor that you must add
> when it's not standard time and week-end (1.5x for for week (during not
> opening hours) and saturday and 2x for sunday). This factor will also be
> applied to users during this time (perhaps a field with an other value
> would be a good thing)
>
> Having fields on the user table with normal working time (would be
> necessary to give the time when he must work), how many hours he must do
> per day/week/month, how many hours overtime is allowed, how many
> holidays he can take per year).
>
> Regarding the ability to assign a task to many projects, I think it's a
> good idea but it will be a little bit difficult because we must also
> manage users rights to this on a task basis (so you will need to give an
> access to a task on a project basis per user, ... It will become a
> little bit complicated).
>
> Why not adding a notion of groups in addition of users and you will give
> rights to groups and not users (so if you add a user, you will not need
> to add it to 200 projects and tasks, ...)
>
> Meilleures salutations / Best regards
>
> Blaise Drayer
> Astron Associates SA
>
> ------------------------------------------------------------------------------
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Tsheetx-developers mailing list
> Tsh...@li...
> https://lists.sourceforge.net/lists/listinfo/tsheetx-developers
>