Table nor working from one day to another - Issue can't be found under Issues but is in Import

Questions & Answers
,
1

Hi,
I got a weird problem.

I did a Dashboard table which shows the Customfield values of a specific projects issue (BAS-1). I’m on EazyBi 6.4.2. I got Issues in Columns and did search and bookmark the specific Issue with it’s name BAS-1. From one day to another the table appeared to be empty and I can’t find BAS-1 under Issues anymore in the table edit. Nobody seems to have done any changes in EazyBi. I checked the Import, the Projects and all it’s customfields are imported. I don’t get any import error. In Jira everything looks good as well. Nothing was changed in the Project or Issue, I’m the only one with acces to it and it’s filled by an Listener everytime somebody tries to push an edit in it.

I’m getting an Error under the System Settings in EazyBi, which I’m not sure if it is linked to my issue:
Failed to make a request to the Jira local REST API URL http://localhost:8080. SourceApplication::HTTPError: Received HTTP 404 error when requesting http://localhost:8080/rest/api/latest/myself.
Google Chrome launching from location “C:\Program Files\Google\Chrome\Application\chrome.exe” failed with GoogleChrome::Browser::StartupError: Cannot connect to port 9261, probably too many parallel export requests.

If anybody can help me, please I have no clue what went wrong.

2

Hi @BackEndTester

I would recommend upgrading eazyBI version and reimporting data to check the report again.

If that still didn’t help, you might want to check if the user who authorized imports from Jira into eazyBI still has access to see the issue in Jira. And if necessary re-set authorization to a different user who can access the issue in Jira.

Next, thing is to check if there aren’t JQL filters in eazyBI import options page that restricts this issue from being imported.

Lastly, check if the missing issue has not been archived or deleted in Jira and project BAS is still imported.

Martins / eazyBI support

3

It was a change in Admins. So the one who authorized it was removed and that lead to my issues. Thank you, I would’ve never thought that those two things were connected.

1 Like