-
Type:
Bug
-
Resolution: Low Engagement
-
Priority:
Low
-
None
-
Affects Version/s: 3.2.0
-
Component/s: Documentation & IX
-
1
-
Severity 2 - Major
-
0
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
With the release of Service Desk 3.2 the release notes mention that Service Desk must first be upgraded to 3.0 before you can upgrade to 3.2. However the migration hub documentation for JIRA 7 upgrades with Service Desk:
https://confluence.atlassian.com/migration/jira-7/server_jira+jsd_upgrade
Makes no mention of the need for an intermediate version to be upgrade to first. This is understandable since this migration guide was created for JIRA 7.0 (and service Desk 3.0) versions. However it would be helpful that if customers are still using JIRA 6.x and wanting to upgrade to the latest versions of JIRA and Service Desk would have some mention of this new upgrade requirement before trying to upgrade directly to the latest version.
- relates to
-
JSDCLOUD-4217 Migration Hub documentation for JIRA Service Desk, update for 3.2 changes
-
- Closed
-
- links to