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

Jira should only re-index once during an upgrade

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      During an upgrade from Jira 3.13.4 to 4.2.2, I couldn't help but notice that issue re-indexing was carried out 4/5 times
      The first re-index is carried out immediately after data import, then a number of upgrade tasks run, 3 or 4 of which carry out issue re-index again.
      Our system has 200,000+ issues in it, and each index job takes approx 90-100 minutes.
      Perhaps all of the re-index jobs are needed, but I can't think of a reason why any more than one re-index would be needed?
      Can Atlassian insert some intelligence into the upgrade process to remove all unnecessary re-index steps?

              Unassigned Unassigned
              b0d88db9bee7 David Corley
              Votes:
              9 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: