Details
-
Bug
-
Resolution: Timed out
-
Low
-
2
-
Severity 3 - Minor
-
Description
Summary
When using "JIRA Issue/Filter" macro users get an error when running a valid JQL query. Running the same JQL query on Jira correctly returns issues, but when trying to use this exact same query on "JIRA Issue/Filter" macro, the search do not return any results and throws the following error:
The JIRA server didn't understand your search query. If you entered JQL, please ensure that it's correctly formed. If you entered an issue key, ensure that it exists and you have permission to view it. Learn More
Environment
- Using "JIRA Issue/Filter" macro, when adding a query containing either "WAS" (e.g. "Status WAS "In Progress"") or "CHANGED TO" (e.g. "Status Changed TO "In Progress"").
- It seems that currentuser() is affected by this BUG on "Assignee was currentuser()" and "Assignee changed TO currentuser()"
- On Jira these JQL queries run like a charm, but running these queries on "JIRA Issue/Filter" macro breaks the macro and the error message above is displayed.
Steps to Reproduce
- Insert "JIRA Issue/Filter" macro into a page;
- Run a JQL query on Jira containing one of these terms, for example " Status WAS "In Progress" ";
- Run the same query on "JIRA Issue/Filter" macro.
Expected Results
- Query should run as expected and results should be displayed exactly like Jira's results
Actual Results
- No issue is returned and an error is displayed:
The JIRA server didn't understand your search query. If you entered JQL, please ensure that it's correctly formed. If you entered an issue key, ensure that it exists and you have permission to view it. Learn More
Notes
This behavior seems related to CONFCLOUD-65276 and CONFSERVER-57861
Workaround
There are currently thee workarounds for this BUG.
1st workaround:
Changing "WAS" to "WAS IN" seems to solve this issue - e.g. "Status WAS IN ("In Progress")";
2nd workaround (recommended):
Adding another TRUE statement to the JQL query seems to solve this issue (any true statement that won't change the result of the query search will do). For example changing "Status WAS "In Progress"" to "Status WAS "In Progress" and project != empty" correctly returned the desired results.
3rd workaround:
Saving this JQL search as a new filter in Jira, and instead of using "JIRA Issue/Filter" to search for issues, use instead "Filter Results" Macro > select the newly created filter.
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
-
- Gathering Impact
-