"Time Tracking Report" Error: Can no longer generate the report

[Jamie Adler]

I have tried for the last few days to utilize the Jira-provided (built-in) "Time Tracking Report" which I have successfully used for the past month. When I configure it and hit 'Next' the result is always an error:

Error Type: 500 - Internal Server Error

Per the warning on that page, I have checked the Statuspage and there is no known outage at Jira. I can't open a Support Request because I am on the Free plan. :( 

Is this just me having this problem? 

I have tried all the various configuration options (there aren't many) in case the issue is arising from one of those. That doesn't help.

What else can I try to do differently? Is it possible some data I entered recently into the worklog is causing the error?

Here is the report I am referring to:

[Andy Heinzer · Accepted solution]

Hi @Jamie Adler I created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-880555

Please approve our request for data access there so that our support team can investigate this further.

Thanks for flagging this to us @Trudy Claspill !

[Jamie Adler]

Done. thank you :)

[Jamie Adler]

This is now working again for me (after a fix by Atlassian in response to the support ticket opened).

[Li Qiang]

We have the same issue in our tenant. 

[Trudy Claspill]

@Li Qiang 

If you are using a paid subscription to Jira have your Jira Administrators open a support case with Atlassian at

https://support.atlassian.com/contact/#/

[Jamie Adler]

FYI @Li Qiang this is now working again for me (after a fix by Atlassian). It may also work for you now.

[Li Qiang]

Thank U! It looks working for me too.

[Trudy Claspill]

Hello @Jamie Adler 

This problem has been reported in a few other posts also.

I have tagged your post to raise it to the attention of the Atlassian Team. One of them will reach out to you.

[Jamie Adler]

Thank you Trudy - I tried searching for similar issues so I could see if it was "just me" or "pile on" but couldn't find any.  Appreciate the help!

[Jamie Adler]

This is now working again for me (after a fix by Atlassian). Thanks @Trudy Claspill !