Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-22214

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

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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

          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