How can I debug a 400 server error when using the 'was' operator with assignee? - for JIRA v8.11.0

David du Toit June 30, 2021

PS: This could possibly be linked to this support ticket.

When I use the was operator (was, was in, was not etc) in a JQL search I receive this error in the UI

jira-wasOperator-error.png

Inspecting the debugging console while doing the search I see that the server responded with a 400 and 500 error on two POSTs

  • POST http://<our-jira-url>/secure/QueryComponent!Jql.jspa 400
  • POST http://<our-jira-url>/rest/issueNav/1/issueTable 500

We followed the suggested steps from the above-mentioned support ticket, but we have a newer version of JIRA and do not have all the settings it refers to.

I do not have access to the server logs and was wondering if there are setting changes, alternative queries or variables I could try to debug what the cause of this error could be?

PS: I am able to use the was operator for status without errors

0 answers

Suggest an answer

Log in or Sign up to answer