-
Bug
-
Resolution: Invalid
-
Low (View bug fix roadmap)
-
None
-
4.1.1, 4.1.2, 4.2, 6.0.6
-
4.01
-
Steps to reproduce:
1. Create a project with versions A, B, C, D, and E (or 1, 2, 3, 4, 5, etc), A being the first version and E being the last.
2. Create a six issues, the first with fix version as A, the second as B, and so on, then one with the fix version as A and E.
3. In the Issue Navigator, run the following JQL query: fixVersion >= "B" AND fixVersion <= "D"
Expected results:
The issues with fix version B, C, and D are returned.
Actual results:
The issues with fix versions B, C, and D are indeed returned, but so is the issue with fix versions A and E.
The same issue occurs if you use just < and > instead of >= and <=.
- relates to
-
JRASERVER-28826 Order version fields by their order on the configuration screen
- Closed
[JRASERVER-22995] JQL query "fixVersion >= B AND fixVersion <= D" returns unexpected results
Minimum Version | New: 4.01 |
Workflow | Original: JAC Bug Workflow v2 [ 2836654 ] | New: JAC Bug Workflow v3 [ 2926049 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2567002 ] | New: JAC Bug Workflow v2 [ 2836654 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1532381 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2567002 ] |
Labels | Original: JQL bughunt_jql ho-jql-backend | New: JQL affects-server bughunt_jql ho-jql-backend |
Component/s | New: Issue Navigation & Search - JQL [ 43398 ] | |
Component/s | Original: JQL [Deprecated] [ 12922 ] | |
Labels | Original: JQL bughunt_jql | New: JQL bughunt_jql ho-jql-backend |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 678438 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1532381 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v5 [ 645994 ] | New: JIRA Bug Workflow w Kanban v6 [ 678438 ] |
We don't have an alternative for this at the moment, sorry.