Log work time isn't possible - the "Save" button is inactive
Asked by Sebastian Spitzer:

Since today I can no longer log working time directly in Jira (JSM \& JSW) - the "Save" button is inactive, although all mandatory fields are filled in.

![Log work time isn't possible yet - the 'Save' button is inactive.png](https://community.atlassian.com/t5/image/serverpage/image-id/346303i7E642647B411565A/image-size/large?v=v2&px=999 "Log work time isn't possible yet - the 'Save' button is inactive.png")

I usually use the keyboard shortcut 'q' for quick entry, but it no longer works this way.  
It also doesn't work if I go through the menu and select "Log work".

Affects Jira Service Management Issues and Jira Software Issues.  
It still worked for some Issues in JSM today, but not for the majority of Issues (JSM \& JSW).  
But I can't see any pattern.

Most recently it worked for all Issues, including last Thursday, September 5, 2024 (my last working day).

Time tracking had already been activated and possible for years.  
However, we have not made any changes to the permissions in our organization.

Our only applicable **workaround** at the moment is to book working time via "Timesheet" as a feature from the "Time Tracker" plugin from third-party provider "Tempo".  
(Feature "+ log time").

![Workaround 'add Logtime' from Timesheet works.png](https://community.atlassian.com/t5/image/serverpage/image-id/346304i89A18138FB980BFC/image-size/large?v=v2&px=999 "Workaround 'add Logtime' from Timesheet works.png")

**Hence the question:**Has there been a Jira update in the last few days that has a negative impact on this (bad fix)?


Answers:
author: Sebastian Spitzer
body: **The problem is currently no longer reproducible!**

Tickets that could not be booked yesterday are working again.

Also confirmed by various users in our Organization.

Seems to have been a "phantom" error, or Atlassian reacted quickly and quietly beyond the date limit. ;-)

I would like to close the question here.

comments: author: Sebastian Spitzer
body: P.S.: We didn't make any changes to the configuration. The solution must have come centrally.


author: Tiina Savolinen
body: This happened for us also if not using english version - workaround:

- at Remaining estimate -field change your min. to m

![N?ytt?kuva 2024-09-10 094706.png](https://community.atlassian.com/t5/image/serverpage/image-id/346481i47A9D818E641D128/image-size/large?v=v2&px=999 "N?ytt?kuva 2024-09-10 094706.png")![N?ytt?kuva 2024-09-10 094910.png](https://community.atlassian.com/t5/image/serverpage/image-id/346482i5A959FFBA57E94E5/image-size/large?v=v2&px=999 "N?ytt?kuva 2024-09-10 094910.png")

comments: author: Sebastian Spitzer
body: Hi [@Tiina Savolinen](/t5/user/viewprofilepage/user-id/5385614) ,

that could definitely have been the reason.

Today it is preset to the expected formats (m, h, d, ...).

Good tip! Eagle eye ;-)  
Thank you!


author: John Funk
body: Hi Sebastian,

I have seen some other users that that if they changed their default language then it starts working. They were set to Dutch (Netherlands) changed to English UK, and they were able to save the time. Give that a try and if so, it is definitely a bug in Jira that has been introduced.

comments: author: Daan Verkooijen
body: This worked for us. Changed from Dutch to English US and now I can log time.


author: Sebastian Spitzer
body: Hi [@John Funk](/t5/user/viewprofilepage/user-id/7148)

Interesting. I don't see any connection between the occurrence of problems in the chronology since today and a default language setting, but I'm happy to try it as a workaround.

Change default language in the user's profile ([Atlassian account](https://id.atlassian.com/manage-profile/account-preferences?ref=jira&src=personalsettings))?  
or  
Default language in the system (Jira) \> General settings \> Default language?  
(/jira/settings/system/general-configuration)

Nevertheless, it definitely seems to be a central bug in Jira when many users acting independently of each other suddenly have the same problem.

Does anyone already know the Atlassian issue (number) for this?


author: John Funk
body: [@Sebastian Spitzer](/t5/user/viewprofilepage/user-id/2135003) - Not sure which language default =- probably start with user profile first and see if that works.

Not aware of the JAC number either if one exists.


author: Daan Verkooijen
body: Exact same issue here. Logging time hasn't been possible since this morning.


author: Deniz O?uz
body: Hi [@Sebastian Spitzer](/t5/user/viewprofilepage/user-id/2135003) ,

There is a downside of your workaround. It is not noticeable until you stop using Tempo. If you are not going to continue with Tempo, you may need to delete your worklogs recorded with Tempo and recreate them if you need author information. [Why do the Jira worklogs appear with the author Tempo Timesheets instead of the user's name? - Knowledge Base Articles - Tempo Confluence (atlassian.net)](https://tempo-io.atlassian.net/wiki/spaces/KB/pages/488931333/Why+do+the+Jira+worklogs+appear+with+the+author+Tempo+Timesheets+instead+of+the+user+s+name)

PS: You can't update worklog author information, only way to fix them is deleting and reinserting them.

comments: author: Sebastian Spitzer
body: Hi [@Deniz O?uz](/t5/user/viewprofilepage/user-id/853375),

okay. We would then forego the workaround with Tempo.

But all the sooner and sooner we need a solution for time tracking in Jira!

And: Is there also an answer to my question in my post?  
***Has there been a Jira update in the last few days that has a negative impact on this (bad fix)?***   


Tags: cloud

jira-service-management

jira-service-management-cloud