Following a S2C migration, reindexing is not automatically occurring resulting in inconsistent JQL results in Issue Search

XMLWordPrintable

    • 40
    • 13

      Issue Summary

      Following a Jira server to cloud migration, Issue Search results via JQL returned inconsistent data:

      For example:

      • text ~ TEXT = 6 issues returned on Cloud

      HOWEVER

      • text ~ TEXT = 20 issues returned on Server

      No issues are deleted on Cloud after migration.

      Reindexing the Jira instance resolved the issue.

      Steps to Reproduce

      1. Migrate Jira from Server to Cloud
      2. On Server, run Issue Search and receive results
      3. On Cloud, run Issue Search and receive different results

      Expected Results

      Reindexing should automatically kick off immediately following a server to cloud migration.

      Actual Results

      It appears that this trigger is inconsistent, and manual reindexing is sometimes required.

      Workaround

      Contact Atlassian Migration Support

            Assignee:
            Unassigned
            Reporter:
            Mio Otsuki
            Votes:
            2 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: