Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
5
-
32
-
Description
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Problem Definition
As per the JIRA Service Desk 3.2.x Release Notes, it is currently not possible to upgrade directly from JIRA 6.4.x and Service Desk 2.5.9 to JIRA Core 7.2.x with JIRA Service Desk 3.2.x. Hence, customers running on JIRA 6.4.x will have to upgrade twice, increasing their downtime and also the upgrade effort to go to JIRA 7.2.x and JSD 3.2.x.
Suggested Solution
As a JIRA administrator, I would like to be able to upgrade from JIRA 6.4.x and JSD 2.5.9 to JIRA 7.2 and JIRA Service Desk 3.2 directly so that I can perform a single upgrade.
Workaround
The following jira-config.properties parameters can be used when upgrading from JIRA 6.4 to 7.0 and Service Desk 3.0:
upgrade.reindex.allowed=false jira.autoexport=false
This will cause the intermediate upgrade path ( JIRA 6.4 -> JIRA 7.0 -> JIRA 7.2 ) to occur much faster as JIRA performs an export and re-index normally as part of the upgrade which takes a long time in larger environments and is unnecessary for intermediate upgrade versions. These parameters can be removed when upgrading JIRA 7 to JIRA 7.2
Attachments
Issue Links
- causes
-
JSDSERVER-4211 Upgrading Service Desk to 3.2 from a version <= 2.5.x causes the sidebar to appear blank with an error 'unable to render element due to an error'
-
- Closed
-
-
RAID-103 Loading...
- is caused by
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
- Closed
-
-
- is related to
-
- mentioned in
-
-
-
-
-
-
-