Forums

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

In List page why are the estimate columns no longer formatted in the desired style?

Jeremy FDLBand
July 14, 2026

The Sum Original Estimate, Sum Time Spent and Sum Remaining Estimate no longer honor the Time Keeping desired formatting.  I am using hours but it shows up pretty unlike the Time Spent column that is in the desired hours.  image.png

1 answer

0 votes
James Gamble
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.
July 14, 2026

Hi Jeremy,

This appears to be a Jira Cloud display issue rather than a problem with your time-tracking settings.

The regular Original Estimate and Time Spent columns are respecting your global Hours setting, but the three columns prefixed with Σ are aggregate fields. They include the value from the parent work item plus its subtasks, and the List view appears to be rendering those totals in Jira’s “pretty” format, such as weeks, days, and hours, instead of using the time display format selected under Settings > Work items > Time tracking.

Atlassian has an existing bug for the same underlying behavior in other Jira Cloud views, where time values ignore the global Hours setting and display in a pretty format instead.

I couldn’t find a separate public bug specifically for the Σ columns in the List view, but the behavior in your screenshot appears to be another instance of that limitation. The global setting is still configured in the location described here, and it should normally control whether Jira displays time as pretty, days, or hours.

Unfortunately, I don’t believe there’s a List-view setting that lets you format those aggregate columns independently. For now, the practical options are to use the non-aggregate columns when you don’t need subtask totals, or report the List-view behavior to Atlassian and reference JRACLOUD-69810 so they can confirm whether it should be tracked under that bug or logged separately.

Thanks,

James

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events