Worklog Report returning blank screen

[jim-mcneill-uk]

Checklist before you being

• [X] I am sure that I am already using latest version of Jira Assistant
• [X] I had verified that, no similar issues are already reported in issue tracker
• [X] I had tried reproducing this issue with with Web version of Jira Assistant to ensure that this issue is not recently fixed and yet to be published
• [X] I had verified that, my query is not answered in FAQ section of website
• [X] I had verified that, my issue is not listed as known bugs in website

How do you use Jira Assistant?

Browser extension

Are you using cloud version of Jira or self hosted (data center / server) of Jira.

Cloud Jira

Version of Jira Assistant

2.58

What browser are you using?

Chrome

What OS are you using? You need not disclose this if you feel it is irr-relevant for your issue.

Windows

Bug Description

The new worklog report is showing a completely blank screen, first error on the console is a 400, Google insight is:

Explanation

The error "400 (Bad Request)" you're seeing with your Atlassian Jira API request indicates that your JQL query is invalid. Specifically, the problem lies in how you're constructing the key in() clause within your JQL.

The Issue:

You're passing '[object Object]' as the value for the key in() clause. This suggests that instead of a proper array of issue keys, you're passing an object or an object representation as a string.

Checklist before you submit

• [X] I have ensured not to paste any confidential information like Jira url, Mail id, etc.
• [X] I have verified my browser console logs and added necessary details (if required)
• [X] I have added required screenshots if the bug is related to UI (as necessary)

[shridhar-tl]

Somehow JQL did not form properly it seems. Please look at the console log and send me the screenshot. Additionally also look at the network tab and the params being passed to JIRA and see how query is formed. Based on the error message you provide, key is passed as stringifyed object "[object Object]". But whether that key is something you added as custom filter or it happens internally is something we need to identify. For that which exact Api call and query fails has to be identified. You network request would provide the required information.

[jim-mcneill-uk]

Do these help?

[shridhar-tl]

Yes, this helps up to an extent. Let me try to see if I was able to figure it out from code.

[jim-mcneill-uk]

I've found that it works on the webapp, sorry I should have checked that out earlier