I get a "Jira Unavailable Service" every time a ask for a Time Reports Report

[Paula Remez]

[Andriy Zhdanov]

Hi Paula,

Looks like you've created another issue for the same problem. But this time, I've realised that problem happens before time tracking data is even loaded.

Could you please open Developer Console in browser, and see Javascript console or Networks tab, to identify which request is actually failing?

It might be that you have too many filters, so that JIRA can't serve needed data.

Thank you.

[Paula Remez]

Hi Andriy. The error message occurs every time I try to get a Time Reprots Report. Even when it's just one report:

These are the errors shown in the console:

The error happens with my user. When, as an administrator, i log in with another user, the error message doesn't happens and everyhings works OK.

When generating Reports whith my user, I can't see the filters: ![reporte con user premez no veo los filtros.png] (https://bitbucket.org/repo/8Xedz7/images/4222470200-reporte%20con%20user%20premez%20no%20veo%20los%20filtros.png)

But when I login as another user, I can see them:

So, I deduce the problem is related to my user....

Thanks a lot!!

[Paula Remez]

I can generate all time reports with my user, but I always get the error message after the report is generated. Filters in the top of the reports are never loaded whit my user.

[Andriy Zhdanov]

Hi Paula,

Could you please copy the url of favorite resource that is failing and paste it into browser address bar and try to open it and see if it works?

If it produces an error for you, could you please open support request with Atlassian?

Thank you.

[Paula Remez]

Hi Andriy. This is the URL: https://mobilecomputing.atlassian.net/rest/api/2/filter/favourite?_=1485429316350

and it gets this response: {"errorMessages":["Internal server error"],"errors":{}}

Ok, I'll open a ticket to Atlassian.

[Andriy Zhdanov]

Issue #1041 was marked as a duplicate of this issue.

[Andriy Zhdanov]

Hi Paula,

In similar problem in issue#1049, problem was caused by sharing group with a group that has been deleted. If this is a case for you too, please inform Atlassian, if possible.

Thank you.

[Andriy Zhdanov]

Issue #1050 was marked as a duplicate of this issue.

[Andriy Zhdanov]

Atlassian is trying to investigate it also here https://getsupport.atlassian.com/servicedesk/customer/portal/22/JSP-283457