According to the last bullet on https://confluence.atlassian.com/jirasoftware/jira-software-7-3-x-upgrade-notes-861251109.html, upgrading from JIRA pre-7.0 to JIRA 7.0 first is recommended, before going to JIRA 7.3.
However, in our case, we are thinking of getting new server hardware with a different OS, so this would actually be a migration of our JIRA instance to a new server. We can do the XML export, backup of attachments and indexes, and then copy the stuff over to the new box. In this scenario, do we still need to start with a 7.0 instance, or can we start with 7.3?
EDIT: We are on JIRA 6.4.12, with Agile 6.7.12, and ScriptRunner 18.104.22.168. We have a few other small add-ons, but not business-critical like ScriptRunner for us. We do not have ServiceDesk.
"Pre 7" does not tell us enough to give you a good answer.
Niclas' answer about Service Desk is right, but there are other considerations
If you are on 6.4 + Agile, you can probably go straight to Software 7.3.
If you are on 6.3, it's a lot less likely to work, and you should not go any higher than 7.1
If you are on 6.0,1,2, then go to 7.0 first
If you are lower than 6, then go to 6.4.14 first, then test a jump to 7.3
And, a lot depends on the other add-ons you have. Some add-ons will break an upgrade from 6.anything to 7.anything-above-0
We are on JIRA 6.4.12, with Agile 6.7.12, and ScriptRunner 22.214.171.124. We have a few other small add-ons, but not business-critical like ScriptRunner for us. We do not have ServiceDesk.
Appreciate the answers thus far. Perhaps it is safest to go to 7.0 first, and then upgrade from 7.0 to 7.3. Anything I lose by going through that route other than time and effort?
6.4.12 to Software 7.3 with latest Agile + Scriptrunner 4 is something I'd expect to work quite well actually.
Of course, I would test it first, and the fallback is definitely 6.4 -> 7.0, but one of my team did a 6.4 to 7.3 this weekend and it sailed through fine. Only hiccup we had in testing was a bug in 7.3.0 that causes a performance issue in some cases, so we took it to 7.3.1 which fixed it.
The main problems we ran into on that one were that the API in 7 changes quite significantly - mostly around how users are coded for, but a lot of older deprecated api calls are also removed. This means some scripts need updating during the upgrade (the extent of that depends on what you've written!), but the worst case is they simply stop working until they're fixed, not damaging data.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs