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: 

incorrect Remaining estimate

Artem Shukman
Contributor
March 12, 2025

Hi team!

i think i found a bug.

How to reproduce:

1. Create task witn any standart type

2. Set  time track 1h.

3. set original estimate 1d

4. set time track 1h and look to field remaining estimate.

There is "0m"... Why?

If you want to collect reports on this field, tasks with this incorrect estimate will not be included to reports and its note good.

Will you fix this?

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Karan Sachdev
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 12, 2025

Hey Artem,

 

With the current product design, it is expected to add the Original Estimate only once, before any time is logged. For detailed explanation on this, please review the explanation shared by the product manager on this suggestion ticket: https://jira.atlassian.com/browse/JRACLOUD-77064

Thanks!

0 votes
Artem Shukman
Contributor
March 12, 2025

For now, there is only one solution - to put the original estimate first. But this is not always possible right away..

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events