Issue Summary
Performing a JQL search using "Target end" or "Target start" dates returns 0 or incorrect results. For example: 'project = "Project name" AND "Target end" is EMPTY' returns data with Target end having actual date not EMPTY. The same for NULL.
Another example JQL that will break: 'project = ABCD AND "Target End" >= '2020-01-01' AND "Target End" < '2020-03-01''
Steps to Reproduce
- Create a project and some issues
- Create a Jira Portfolio plan using the new project
- Update some issues in the plan with a "Target end" or "Target start" date
- Perform the JQL search 'project = "Project name " AND "Target end" is EMPTY' or 'project = Blah AND "Target start" >= '2020-01-01''
- Note the results return as expected.
- Complete a Full reindex.
- Repeat the same JQL searches.
Expected Results
Return only issues with Target end where it's empty or returns the issues that meet that the JQL parameters. Note: Before the reindex, expected results are found. After the reindex they are not.
Actual Results
It returns all data for both empty Target end date and non-empty.
Workaround
A background index will temporary remediate the issue. No permanent solution has been found.
- is caused by
-
JPOSERVER-2740 A full Jira index does not index Portfolio's custom field values that are stored as entity properties resulting in incorrect JQL query results
-
- Closed
-
- causes
-
GHS-174791 You do not have permission to view this issue
- is cloned by
-
JPOS-4830 You do not have permission to view this issue
[JPOSERVER-2727] JQL searches using "Target end" or "Target Start" dates return 0 or incorrect results
Resolution | New: Fixed [ 1 ] | |
Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
Status | Original: Short Term Backlog [ 12074 ] | New: In Progress [ 3 ] |
Fix Version/s | New: 3.21.0 [ 91507 ] |
Assignee | Original: Quentin Feyaerts [ qfeyaerts@atlassian.com ] | New: David Shaw [ dshaw2@atlassian.com ] |
Assignee | New: Quentin Feyaerts [ qfeyaerts@atlassian.com ] |
Affects Version/s | New: 3.20.0 [ 91203 ] |
UIS | Original: 178 | New: 365 |
Link |
New:
This issue is caused by |
In a DC cluster, the background or project reindex is only effective until the issues are modified (eg modify the issues on another node in the cluster) - queries then return wrong results again