Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,466,614
Community Members
 
Community Events
176
Community Groups

Incorrect calculated remaining estimate

While using subtasks, the "Include sub-tasks" option under "Time Tracking" causes incorrectly calculated values for "Remaining". Especially deleted worklogs seems to lead to incorrect calculations.
In general, deleted worklogs cause remaining times, even if no original estimated was set before. That doesn't seem logical to me.

tempo version: 8.12.1
jira version: 7.3.6

1 answer

0 votes

Hi @Hendrik Schmidt 

It would be great if you could give use an example. Usually thins work pretty good I don't have any problem with it.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events