We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-76991

Some historical JQL searches return additional issues

XMLWordPrintable

      Issue Summary

      Historical JQL searches that use WAS  with DURING or AFTER or ON. Might give inaccurate results. They might return additional issues.

      Steps to Reproduce

      1. run of one following JQLs:
        1. <field> WAS X DURING (A, B)
        2. <field> WAS X AFTER A
        3. <field> WAS X ON A

      Expected Results

      Correct issues are returned.

      Actual Results

      In some rare cases, JQL will return additional 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 history of some issues. Only JQL is affected as that data is only used by JQL engine.

      Workaround

      If you are experiencing the problem described in this ticket please contact Atlassian support so we can assist you in fixing it.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Platform Cloud'
            1. Jira Platform Cloud
            2. JRACLOUD-76991

            Some historical JQL searches return additional issues

            XMLWordPrintable

                Issue Summary

                Historical JQL searches that use WAS  with DURING or AFTER or ON. Might give inaccurate results. They might return additional issues.

                Steps to Reproduce

                1. run of one following JQLs:
                  1. <field> WAS X DURING (A, B)
                  2. <field> WAS X AFTER A
                  3. <field> WAS X ON A

                Expected Results

                Correct issues are returned.

                Actual Results

                In some rare cases, JQL will return additional 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 history of some issues. Only JQL is affected as that data is only used by JQL engine.

                Workaround

                If you are experiencing the problem described in this ticket please contact Atlassian support so we can assist you in fixing it.

                        f0f4433adc59 Jędrzej Herbik
                        kgrinholc Kamil Grinholc
                        Votes:
                        27 Vote for this issue
                        Watchers:
                        61 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            f0f4433adc59 Jędrzej Herbik
                            kgrinholc Kamil Grinholc
                            Affected customers:
                            27 This affects my team
                            Watchers:
                            61 Start watching this issue

                              Created:
                              Updated:
                              Resolved: