Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-78497

Historical JQL searches return wrong results after applying workaround(JRACLOUD-84058)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low (View bug fix roadmap)
    • None
    • 10.0.0
    • JQL
    • None

      Issue Summary

      Customers might experience trouble running historical JQL searches using WAS/WAS IN with BEFORE/AFTER/DURING/ON.

      Steps to Reproduce

      Run one of the following example JQLs:
      status WAS closed DURING ('2024-01-01', '2024-01-31')
      assignee WAS currentUser() AFTER/BEFORE startOfYear(-1)
      priority WAS P1 ON '2024-01-01'

      Expected Results

      Issues within the date range and condition are returned.

      Actual Results

      In some cases, the historical JQL search will return additional issues or no issues. Issues that had value X set to <field> before A but it has been later (before A) changed.
      This is caused by corrupted data in the history of some issues. Only JQL is affected, as that data is only used by the search engine.

      Workaround

      The workaround shared under ticket: https://jira.atlassian.com/browse/JRACLOUD-84058 is not working

            [JRASERVER-78497] Historical JQL searches return wrong results after applying workaround(JRACLOUD-84058)

            Aditya Dewan made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 988695 ]
            Aditya Dewan made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 988576 ]
            Jacek Foremski made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Maria Marzec made changes -
            Component/s Original: Migration - Server to Cloud [ 43413 ]
            Component/s New: JQL [ 43398 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Bugfix Automation Bot made changes -
            Introduced in Version New: 10
            Gabriel Aguilera created issue -

              Unassigned Unassigned
              24687bbc775d Gabriel Aguilera
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated: