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
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Release Notes
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Original time estimate is displaying incorrect value (It adds 4h to the value I enter)

Amin Heidari
Amin Heidari
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
September 26, 2022

When I enter an original estimate of less than 4h (up to 3h 59m) it is displayed (and summed up correctly in sprints) on the backlog.

However, if I enter anything 4h and above and save, an additional 4h is immediately added to it!! So 4h shows up 1d, and 5h shows up 1d 1h! These incorrect numbers are used to show the total estimates in sprints/backlog as well. So for example two 4h stories sum up to 2d (1d + 1d) in a future sprint on backlog :(

This is very likely (partially) a UX-only issue, because when logging work, the correct original estimate is used. Here's an example:

- I enter 4h as original estimate, it shows up 1d.

- I log 1h of work, and remaining work is 3h (and not 7h).

Is anyone else facing the same issue? Hopefully this is a temporary defect that Jira will fix! 

Watch
Like Be the first to like this
1255 views

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
Get recognized
September 26, 2022

This looks like an error in your configuration, Jira is working as it should.

I think one of your administrators has set the (global) time settings to 1 day = 4 hours.

Go to Admin -> General -> Time settings and change it to what your day should be (sounds like 7 hours in your post)

View More Comments
Amin Heidari
Amin Heidari
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
September 26, 2022

Thank you very much.

Like ā€¢ Nic Brough -Adaptavist- likes this
Reply
Jira
Jira
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Release Notes
    Copyright © 2026 Atlassian
    Privacy Policy Notice at Collection Terms Security