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

CLONE - Remove any re-index from the JIRA 4.1 upgrade tasks that's not needed

    XMLWordPrintable

Details

    • 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.

    Description

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

      This is a clone of JRA-18493 which was resolved as fixed.

      During an upgrade from Jira 3.13 to Jira 4.1.2 two re-indexes occur, one for Build 440 and one for Build 518.
      Please reduce this to one if at all possible.

      On a system with many issues, like 200000, this double re-indexing consumes 2 hours of site down time instead of 1 hour.
      In our upgrade from Jira 3.13 to 4.1.2, we need to manually re-index a third time as we have dropped and then re-added a custom calculated field that changed due to changes in the Jira API.

      Attachments

        Issue Links

          is related to

          Suggestion - JRASERVER-22214 CLONE - Remove any re-index from the JIRA 4.1 upgrade tasks that's not needed

          • Closed

          Activity

            People

              jed Jed Wesley-Smith (Inactive)
              adc6ee404f6d Jeff Kirby
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2h
                  2h
                  Remaining:
                  Remaining Estimate - 2h
                  2h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified