Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.13.0
-
None
-
8.13
-
5
-
Severity 2 - Major
-
5
-
Description
Issue Summary
A JQL search using a single sprint name may pass multiple sprint IDs in the Lucene search query. Also, it can pass IDs of the matching sprints in the Lucene query even if there isn't any sprint with the name being searched in the JQL query.
Steps to Reproduce
Create three scrum software Projects with the details as in the screenshot below:
Now, say a user user1 makes a JQL search
sprint in ("SCRUM")
OR
sprint = "SCRUM"
Expected Results
JQL search shouldn't show any results as there are no issues in sprint with "SCRUM"
Actual Results
JQL search also shows issues under sprints SCRUM1 and SCRUM2.
As checked in the logs JQL query
{sprint in ("SCRUM")} is converted to Lucene query (customfield_10104:22 customfield_10104:23 customfield_10104:24)where,
22 = Sprint ID of sprint SCRUM1
23 = Sprint ID of sprint SCRUM2
24 = Sprint ID of sprint SCRUM
2021-10-29 21:01:36,803+0530 http-nio-8080-exec-14 DEBUG asdf 1261x9265x2 193q1lh 127.0.0.1 /rest/issueNav/1/issueTable [c.a.j.i.search.providers.LuceneSearchProvider] JQL query: {sprint in ("SCRUM")}
{code:java}
2021-10-29 21:01:36,803+0530 http-nio-8080-exec-14 DEBUG asdf 1261x9265x2 193q1lh 127.0.0.1 /rest/issueNav/1/issueTable [c.a.j.i.search.providers.LuceneSearchProvider] JQL lucene query: (customfield_10104:22 customfield_10104:23 customfield_10104:24)
converted Lucene query should be (customfield_10104:24) only
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available