workTimer work flow using workdays and hours per day Follow
I'd like to use some workflow to automatic add "Spent time" to tracks when using Time tracking. But workTimer default workflow doesn't support working days, hours per day etc.
I there any WF which does? Why are Workdays and Hour per day in settings, when I is not used at all? It's good enought to limit max. work time per day to set value (etc. 8 hours) and exclude weekends. Currently when I put task to state In process on Friday morning and set it as Fixed on Monday, it adds me e.g.60 hours - it's not useable at all.
Thx for any advice.
I there any WF which does? Why are Workdays and Hour per day in settings, when I is not used at all? It's good enought to limit max. work time per day to set value (etc. 8 hours) and exclude weekends. Currently when I put task to state In process on Friday morning and set it as Fixed on Monday, it adds me e.g.60 hours - it's not useable at all.
Thx for any advice.
Please sign in to leave a comment.
As workaround you can define the day of week by the string Timer time.format(#e);
Also the following workflow should take into account work hours, please try:
Let's say I finished my work 10 hours after it has been started.
hours = 10 - 16 * ((10+8)/24)
hours = -2
That is wrong, isn't it?
I tried also count actual time, day of week etc. But I don't know, how to set date variable properly.
Let's say I need to count first day spent time as: Timer time.date at 18:00 - Timer time.time. How to set any variable this way?
I tried
But timerEvening is becomes value in this case, not date time value. And I didn't find any way how to use some "semi constants"like this.
Any other idea?
Unfortunately you cannot create a date field from scratch.
All weekends and hollidays are not counted into final sum (there is list of Czech hollidays exclude Easter Monday).
Hi! I've started working on a solution for this problem, but am new to programming workflows. I'm wondering if you can point me to documentation about both Timer and also what language features are supported. To my front-end eye the code looks very Javascript-y and I'm wondering what's supported and not. Thanks!