I have a space where I cannot save time tracking from the BOARD view. This error occurred for the first time on May 4th, 2026. It was working before.
I need to open the specific task in full mode to be able to registrate time
The time tracking in other spaces does work properly from the BOARD view.
What is the difference?
Can confirm this is currently occurring for our organization as well. We have a ticket open with Atlassian support for it.
That will confirm what I think and point in direction Regress.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian has confirmed this is an internal issue and they have engineers working on it. It sounds like the Incident Management team decided the impact wasn't big enough to put anything on the Status page about it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Matt, Thank you for this update
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Rob Franssen
Since this issue popped up right around May 4 and worked perfectly before that, your first stop should be the Jira audit log for that specific space. I'd look for any tiny tweaks made around that date, specifically changes to project permissions, field configurations, or even a small update to the workflow or time-tracking settings.
Sometimes a "small" layout change can accidentally hide or break a field's ability to save correctly on the board view.
If you find that the configuration hasn't been touched, but your users can still log time from the full issue view while the Business board keeps failing, you’re likely looking at a bug in the board's frontend. Since we can't peek under the hood here in the Community, that's when you'll want to flag this to Atlassian Support. Make sure to give them the space type, a specific issue key, and a quick screen recording of the error. That frontend "save" action on the board can be a bit temperamental, and they'll be able to see if there's a backend mismatch causing that save to fail.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Arkadiusz Wroblewski Thank you for thinking along. I see from Matt's point the issue has been recognized by Atlassian and they are working on it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Rob Franssen ,
Are you using the default time tracking functionality of Jira? Or are you using an AddOn?
Have you compared the screen configuration of the different spaces?
Are they both the same type of spaces (software / business / ...)?
Best regards,
Kris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are using the standard Jira time tracking. No add-on.
The space in error is a "Business" Space. The other ones which are working OK are a "Software" space.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.