I accidentally set a large number of Working hours per day and Working days per week and now the whole Time tracking is broken and the work logs can’t load nor can be recorded.
On Settings / Issue Features / Time tracking page there is just a dropdown with a single item JIRA provided time tracking and the rest of the page is empty.
When clicked on a Work log at an issue, an error appears: We couldn't load the worklog.
Thank you very much,
Welcome to Atlassian Community!
Testing on my local site, I logged time 19 times and it loads, so I would like to know more details about your use case.
Do you remember approximately how many times you logged hours/minutes on the ticket?
If you click on the Time Tracking field, does it load or it shows an error?
Can you please open the developer tools on your browser and check on the console tab if it shows any other error when you try to view the Work log history?
Is this issue happening if you view the History tab on the ticket as well?
Have you tested using another browser?
I didn’t find any ongoing bug with Worklog, just a feature request to limit the results:
Please, let us know the details so we can try to replicate the same issue here.
Thank you, Angélica, for looking into the problem, I appreciate it. To your questions:
Some more information:
I think the problem lays in some weird data in the database where default values for timetracking are stored (Working hours per day and Working days per week). As I mentioned in my original post, I accidentally put very large numbers into these 2 fields and since that all timetracking is broken and the Configure time tracking page does not load correctly. Since I can not reach the database I have no means how to correct the values. My guess is the core tries to recalculate any data that come from or to the database but gets overbuffered.
Should you try to reproduce the problem, please replace the 2 values of Working hours per day and Working days per week at the Settings/Issue Features/Time tracking page for something unexpected and large, such as "999999" and "999999". That's what I did.
Thank you very much,
Thank you for the details, Milan.
I was able to replicate the same issue on my site and based on that, I created a bug since the Time tracking shouldn’t allow adding more than 7 days and 24 hours on the settings.
I created a ticket on your behalf since we need your consent to access your site and the database to fix the issue.
Please, access the ticket below and click on “Approve data access”:
Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events