-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
High
-
Component/s: Plans - Settings
-
None
-
3
-
Major
Issue Summary
Jira plans interprets '-' in JQL clauses of filter issue sources as a not operator. This is not the case for filters executed elsewhere in Jira
This can be the case for the summary field, both with hyphens at the start of the text and in the middle:
- summary ~ "hello - there" ORDER BY created DESC
- summary ~ "- there" ORDER BY created DESC
And also in short text fields:
- "customtext[short text]" ~ "test - here" ORDER BY created DESC
This is not an exhaustive list, it likely occurs for other field types too.
Steps to Reproduce
1. Create a project with 3 issues:
-
- An issue with summary AAA report
-
- An issue with summary BBB report
-
- An issue with summary CCC report
2. Create a filter with JQL summary ~ "- AAA report". The filter displays the issue with summary AAA report.
3. Create a plan with the filter as issue source.
Expected Results
The plan displays the issue with summary AAA report.
Actual Results
The plan displays the issues with summaries BBB report and CCC report.
Workaround
Escape the hyphen character in the JQL, explicitly telling the search that you want to interpret it as a plain text character:
his can be the case for the summary field, both with hyphens at the start of the text and in the middle:
summary ~ "hello \\- there" ORDER BY created DESC summary ~ "\\- there" ORDER BY created DESC "customtext[short text]" ~ "test \\- here" ORDER BY created DESC
These should all function as intended