The time is being added to the time tracker incorrectly

[Dan Murray]

I created this nifty time tracking automation. It works pretty well but I've noticed a bug. When a ticket is being worked on for a few days the time being added to the time tracker is going in by weeks when the ticket was created a few days prior. I added an example of how the time goes appears. Here's how the automation works. When you change the status of the ticket from "Waiting for assignment" to "In Progress" the current time is entered in the "Actual Start" custom field. When you change it to "Ticket Paused" the current time goes into the "Work Paused" fields. Then the automation takes the time and calculates the difference between both times and gets entered into the "Time Tracker." Please let me know if you have an idea of what's going on or if you need more information.

[Wojciech Wardaszko [HeroCoders]]

Hi @Dan Murray

The most likely reason why your time tracker tracks weeks within days is that your "timer" runs all the time with no respect for work hours, and in Jira, 1 day is 8 hours by default, and a week is 5 days, so after 40 hours you end up with a week of time tracked.

Getting automated time tracking right is a very challenging endeavor. There's a very good reason why time-tracking apps are among the most often installed in the Atlassian Marketplace.

I sincerely recommend considering using such an app. I can vouch for our (HeroCoders') apps: Clockwork Lite or Clockwork Pro. They offer three time-tracking modes, including fully automated based on issue transitions, respecting work hours and - in Pro - holiday calendars.

They also offer robust reporting with timesheets and personal calendar view for convenient review of tracked time. Pro also has integration with Outlook and Google Calendar, so tracking time spent on scheduled meetings is a breeze.

Ping me here if you have any questions.

Cheers!

[Marc - Devoteam]

Hi @Dan Murray 

Whenever you ask for help with an Automation Rule it will help us to help you if you provide:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of any relevant actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. Explain where the issue is.

These questions are not for not willing to help, but to have community members understand on how automation works.

Furthermore, worklogs are stored in seconds, in your automation you would need to convert this.

Example in other community post: https://community.atlassian.com/t5/Automation-questions/Sum-up-logged-work-on-tasks-to-epic-level-double-counting/qaq-p/2012555

[Dan Murray]

There are a few automations involved. I'll label them in bold.

Adds time stamp to the "Actual Start" Custom Field

Adds time stamp to the "Work Paused" Custom Field

Ticket Restarted Automation

Adds time stamp to the "Actual End" Custom Field