Can you please provide an update? It's indicated that work commenced on this in May 2021, however the issue is not resolved.

Update to the last message: I see that the non-editable logged time in the Activity > Worklog section of the issue still does not respect the Time Tracking setting. It appears as "pretty" regardless of setting:
 

With this in mind, would the watchers of this issue be ok with me changing its title to "Time tracking logged time format does not respect Time Tracking setting in Activity > Worklog section".

I can no longer reproduce this behaviour.

Steps to Reproduce
Navigate to Global Settings → Time Tracking and set Time display format as hours
Create a Scrum project, an issue in that project and log some work (more than 10 hours)
From the Board View click on one issue to open it in the New Issue View
[...]
The Time Tracking section in the view shows the time logged in weeks, days, hours, minutes (Pretty view)

Here are my Time tracking settings:

And here you can see that the time has been correctly logged as hours, not in the pretty format:

If the watchers of this issue agree, I believe this ticket can be closed, but I will wait a week before doing so in case anyone disagrees. Thanks!

p.s. There is a somewhat related bug regarding the time tracker field Start date here: JRACLOUD-77988 – Time Tracking (Log Work) date format does not respect the time format set as per the Language setting

Working on this, please also make sure to include an option to select additional options for "pretty" format. E.g. to display only minutes and hours. Without days and weeks. Thank you.

https://getsupport.atlassian.com/browse/JST-669960

Hi Jira People,

It would benefit my operation to NOT SHOW WEEKS in Jira, before it showed each task as total of Hours, but now now it shows Weeks and it is slowing us down ALOT, and Our clients are hot happy, as weeks are very open concept and not accurate enough for counting hours on tasks.

Please tell me how to change the total hours to HOURS and not weeks, you have made Jira much worse tool and I hope you fix this.

This is URGENT, thank you!

regard,
Jon Trausti

https://getsupport.atlassian.com/browse/JST-652437

Project level setting would be better for same reasons mentioned previously.  Does create confusion for customer billing of services.

I'd like this setting to be at a project level as we have some projects on 8h days, and some on 6h days.  

Displaying time in hours gets around this issue, but anywhere where it converts to pretty format, displays it wrong depending on what project we're looking at.

3d 2h = 20h for project A
3d 2h = 26h for project B

This ticket was created almost 3 years ago so it's baffling that it's still not resolved. Can't be that hard, or can it? I often find myself apologizing to our clients using our Jira instance with a "yeah, it's a known bug, they're working on it." Can you maybe bump the priority on this a little?

Please fix this ASAP. Yet another reason not to move to Jira Cloud.

Please add this.  All of our reports are based on hours, and different groups use different definitions of 'day'.  We need to have everyone consistently looking at 'hours'.

I appreciate a fix as well very soon as we have a worldwide used instance and some teams work with an 8h day and some with a 7.4 h day (due to 5x7.4 = 37hours peer week). By always seeing wrong numbers in days, there are wrong assumptions made by affected employees.

So, for me this is a critical bug. I need to see hours everywhere - as at least an hour is an hour everywhere .

+1. Please fix.

+1. Please fix this, this is really annoying !!

+1

We estimate projects by hours, developers log their time by hours, Jira global time display is in hours, but Jira issue new view will not display in hours, come on!

@fonda, thanks for the 999-tip - that helped us a lot!

Why is this still not fixed? You can see that Jira renders tickets in hours initially but then converts it back to the "pretty" format - really not helpful. We need to see everything in hours only.

The workaround of changing working hours and days to 999 won't do for us because we need to ensure working hours are 8 for reporting purposes.

This is an easy fix and SO valuable!! For once, Atlassian, can you please work on something useful rather than focusing on new functionality/crap that people won't use?

+1

+1

This issue is very critical for us.

We are selling 7 hours per day at our customers so dev team works 8 hours per day. Due to this issue, if the developpers dont know this rules, we can loose 14% of our revenues

Show all logged work just as hours, everywhere! How many hours are 2d 2h? We have a 40h cap, has that been reached? How long is a day? How many hours would 1w 4d 1h be? That's too much cognitive work.

Also, don't put "Yesterday" and such on dates. I needed to see the exact minute and/or copy-paste the date/time into the Log work dialog.

Yes this is a huge blocker for all our users …how long will you take to converts 5w 3d 4h 25m logged into hours and than into man-days in your head?

Yes, we still need to invoice man-days to our customers.

I believe that computers were designed to do complex math tasks so humans may do the creative ones.

Thanks for sharing the feedback with us, we greatly appreciate it. In the spirit of being open, our team is looking at a range of improvement opportunities and and have made the decision to investigate this challenge after we started migrating people to new issue view starting March 31 2021. If this is a blocker for you to move to the new issue view, you can let us know by commenting on this page.

We're using Tempo so we don't even want the built-in time tracking to show up on the new issue view, but since there's no way to disable it, fixing this bug would at least allow multiple teams to not be confused about their time logged.

As requested by Atlassian support, some feedback on how this affects us.

Our staff enters their estimates and all other time tracking related values in hours. Mostly this consists of issues of not more then 8 hours, but some issues are deliberately a lot larger (a way for us to track reserved time) which then shows times like "1w 2d 2h". This makes understanding the current remaining time a lot more complicated then needed. 

I'd like to add that this occurs in the sidebar-type view as well as the modal-type view. Also the log work dialog is affected by this bug.