What are the impacts of incorrect time tracking (working hours)

Hi I am new to JIRA and wanted to know what the effects would be on our reporting if our working hours for a day are defaulted to 8 when we are contracted for 7?

I'm told there will be no impact but surely if you plan a task ahead of a sprint to take 10 hours but it actually takes 14 this could cause your reporting to be skewed?  If I log time spent as 2days this would be 16hours?

Being new to JIRA I don't fully understand to impacts to our reporting and subsequent output.

Would appreciate some enlightening!

1 answer

You're right in saying there will be an impact, for excactly the reason you mention. 2d is 16 hours in your setup.

That's something I have to deal with too. My instance is used by several offices worldwide, some of who use 8-hour days, some with 7.5. We generally encourage using hours and not day/week notation when making estimates. Something that takes more than 10-15 hours is probably not broken down enough anyway.

Is there a reason why you have to leave the default 8-hour and not change it to 7-hour days? Because this is very simple to change in the administration menu, in System/Time Tracking.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Jira

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,089 views 0 8
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you