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

XMLWordPrintable

    • 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

            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

            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

            Alex [Atlassian,PSE] added a comment - - edited

            On a single node DC test instance, I was able to replicate the problem by:

            • Install JPOS 3.18.0 or JPOS 3.18.1 on Jira 8.5.2
            • Create two epics, and use Portfolio to assign Target Start and Target End Dates. Commit the changes to Jira
            • Perform JQL project = "Project name " AND ("Target end" is EMPTY OR "Target start" is EMPTY)
              • Note that the two epics do not show, as we added a target start/end date
            • Perform a full lock reindex
            • Perform the same JQL search
              • Note that the two epics now show, even though they shouldn't match the JQL filter  
            • Perform a background reindex
            • Perform the same JQL  search
              • Note that the epics do not show again – the problem is fixed

            So, the issue seems to start from after a full index is performed

            Rolling back JPOS to 3.17.0 resolves the problem and reverts back to the intended JQL search behaviour

            Note, that if you add the Target Start/End columns to the JQL browser, you'll see they show the actual intended value, even though they should not be returned by the filter

            Alex [Atlassian,PSE] added a comment - - edited On a single node DC test instance, I was able to replicate the problem by: Install JPOS 3.18.0 or JPOS 3.18.1 on Jira 8.5.2 Create two epics, and use Portfolio to assign Target Start and Target End Dates. Commit the changes to Jira Perform JQL project = "Project name " AND ("Target end" is EMPTY OR "Target start" is EMPTY) Note that the two epics do not show, as we added a target start/end date Perform a full lock reindex Perform the same JQL search Note that the two epics now show, even though they shouldn't match the JQL filter   Perform a background reindex Perform the same JQL  search Note that the epics do not show again – the problem is fixed So, the issue seems to start from after a full index is performed Rolling back JPOS to 3.17.0 resolves the problem and reverts back to the intended JQL search behaviour Note, that if you add the Target Start/End columns to the JQL browser, you'll see they show the actual intended value, even though they should not be returned by the filter

            Lachlan G (Inactive) added a comment -

            I can reproduce with Target Start as well.

            Lachlan G (Inactive) added a comment - I can reproduce with Target Start as well.

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

                Created:
                Updated:
                Resolved:
                Archived: