The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Tempo Time Tracking Help

Ben Weisman
Contributor
July 20, 2022

Can someone help me make head or tails of this? The original estimate field has 1d and 4 hours in it (28 hours). For some reason it says 12? Also, 31 hours have been logged and it says 10 hours remaining? Which would be 41 estimated hours?? I'm lost.

 

Screenshot 2022-07-20 150023.png 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Dave Rosenlund _Trundl_
Community Champion
July 20, 2022

Hi, @Ben Weisman.  To answer to your question, more information about how things are configured on your end will be needed.  I.e., not sure a fellow community member will be able to help you with the info. provided.

Please consider contacting Tempo support directly, instead.

Best,

-dave

Ben Weisman
Contributor
July 20, 2022

I understand @Dave Rosenlund _Trundl_ but can you think of any reason that the #s would add up this way? The math is nonsensical?

Dave Rosenlund _Trundl_
Community Champion
July 20, 2022

Hi, @Ben Weisman. I can.

Most likely it is because something, somewhere, in Jira and/or Tempo, is configured incorrectly (i.e., not matching up with the other side) — which is producing unexpected results.   

At least, that's an educated guess

The best way to get to the bottom if this quickly is to talk to an expert with whom you can share some details about your environment and can help you find the route cause.

-dave

TAGS
AUG Leaders

Atlassian Community Events