Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-2727

JQL searches using "Target end" or "Target Start" dates return 0 or incorrect results

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • 3.21.0
    • 3.18.0, 3.18.1, 3.19.0, 3.19.1, 3.20.0
    • Usability
    • None

      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

      1. Create a project and some issues
      2. Create a Jira Portfolio plan using the new project
      3. Update some issues in the plan with a "Target end" or "Target start" date
      4. Perform the JQL search 'project = "Project name " AND "Target end" is EMPTY' or 'project = Blah AND "Target start" >= '2020-01-01''
      5. Note the results return as expected. 
      6. Complete a Full reindex. 
      7. 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. 

            [JPOSERVER-2727] JQL searches using "Target end" or "Target Start" dates return 0 or incorrect results

            David Shaw made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Lachlan G (Inactive) made changes -
            Status Original: In Progress [ 3 ] New: Waiting for Release [ 12075 ]
            Lachlan G (Inactive) made changes -
            Status Original: Short Term Backlog [ 12074 ] New: In Progress [ 3 ]
            Quentin Feyaerts made changes -
            Fix Version/s New: 3.21.0 [ 91507 ]
            Quentin Feyaerts made changes -
            Assignee Original: Quentin Feyaerts [ qfeyaerts@atlassian.com ] New: David Shaw [ dshaw2@atlassian.com ]
            Quentin Feyaerts made changes -
            Assignee New: Quentin Feyaerts [ qfeyaerts@atlassian.com ]
            David Shaw made changes -
            Affects Version/s New: 3.20.0 [ 91203 ]
            SET Analytics Bot made changes -
            UIS Original: 178 New: 365
            David Shaw made changes -
            Link New: This issue is caused by JPOSERVER-2740 [ JPOSERVER-2740 ]

            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

            Deleted Account (Inactive) added a comment - 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

              dshaw2@atlassian.com David Shaw
              estorch Eric Storch (Inactive)
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: