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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Is there a way to have an original estimate and updated estimate documented seperately?

We're trying to find a simpler way to record the difference between the time originally estimated on an issue, and the updated time if somebody runs into a problem they didn't anticipate. Is there a field for this I haven't found?



1 answer

0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 29, 2023

Hi @Jess Payne , there are two methods I would suggest. First the way time logging works it addresses this inherently. You provide the Original Estimate and then log time at which point you can change the remaining time. By changing the remaining time you are basically re-estimating and this is all recorded in the History. If this behavior is not suitable then consider adding a custom field to record your new estimate.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events