Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-83057

Historical search [status was (not)] results too many issues (post-migration corruption)

    XMLWordPrintable

Details

    Description

      Issue Summary

      Sometimes after the migration, some issues will not have initially populated records in `changeitem`. Without those initial records the historical search like `status was "To Do" ON 2024-01-12` will not work correctly and some additional issues will be returned in the result list. 

      Note: "changeitem" is the database table which corresponds to the issue history in UI

      Steps to Reproduce

       Steps to reproduce will only work on local dev instances because this problem exists only in some post-migration. tenants 

      1. Create a new issue.
      2. Find the record in `changeitem` table correlated with the newly created issue. 
      3. Remove the founded record in `changeitem` table.
      4. Execute JQL: 
        issuekey = <new created issue key> AND status was not "To Do" ON <date before issue creation>
        

      Expected Results

      A newly created issue should not be visible for the provided JQL

      Actual Results

      Newly created issues will be visible. (Not possible because the issue can't be in that status before even the issue was created)

      Workaround

      Unfortunately, there is no workaround for now.

      Attachments

        Activity

          People

            c0203fad96e0 Dominik Kaliszewski
            c0203fad96e0 Dominik Kaliszewski
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: