Automating worklog, excluding non-working hours and weekends

Question

Hey team, looking to get some advice on an existing automation rule that I have in place.

'Logging work' is new for our team and to avoid slowing down our devs workflow or repeating reminders to fill in the worklog, we put together automation to log the time based on the time differences of two statuses (in progress > code review).

The first step is, we log a start date as noted below, followed by the second rule of logging that work (both rules were found in the community thread, so big thank you to you all!)

My concern is that it doesn't seem to be catering to business hours/days, therefore the worklog isn't accurate.

I read in this thread that I could add 'businessDays', however, I'm not actually sure where to place this and if this would fit my current rule.

Any suggestions would be greatly appreaciated - Thanks in advance!

Valeriia_Havrylenko_SaaSJet · Answer

Hello @Allan Vaifale

As an alternative , I guess you can try Time in Status  for Jira Cloud (developed by my SaaSJet team) here you can create several calendars and add info about your work schedule.

Also you will have 7 types of status time reports to quickly analyze your work and improve processes.

For example The Time in status report shows how long an issue has been spent in each status.

The Assignee time report displays how long it takes each team member to solve a task.

Our add-on has 30-day free trial version and free up to 10 users .

Please, let me know if you have any questions

Hope it helps,

Valeriia

Gracjan Wesołowski _HeroCoders_ · Answer

Hi @Allan Vaifale

If you would like to consider using a third-party app for time tracking that has built-in automatic timers, I can recommend our Clockwork Automated Time Tracking & Timesheets Free app. I believe it fits well in your needs.

You can use, and set up your workflow statuses to automatically start tracking time whenever an issue is in "active" status:

It also calculates overnight/over-the-weekend time based on working hours.

If you have any questions, you can contact us using our Help Center.

Cheers!

Gracjan

Curt Holley · Answer

Hi @Allan Vaifale 
The problem with this approach (to automating time tracking) is, even with business days added in, it is still a 24 hour clock. So if something is "In progress" overnight, then moved to "code review", it will record that it was "worked on" all night.
Plus, this approach implies that someone is actively working on the issue the entire time it is in progress. no lunch breaks, meetings, or other time out is factored in.
If automating time tracking is the only way time tracking will be recorded in Jira, it really does raise the question "What is the value of time tracking in Jira?"
You say it is new (Time tracking in Jira), who and what motivated this move? What is the outcome "they" are looking to achieve?