recommended upgrade path


We need to upgrade our Jira to a Windows Server 2016.
Now, the old version we have is the 4.4.4

I first tried 4.4.4 > 5.2 > 6.4 > 7.0 > 7.5.2

However I found out that 4.4.4 can be imported by 7.0 directlty.

Could you tell me what the recommended upgrade path is in this case?

a)  4.4.4 > 5.2 > 6.4 > 7.0 > 7.5.2

b)  4.4.4 > 6.4 > 7.0 > 7.5.2

c)  4.4.4 > 7.0 > 7.5.2

As I installed Jira on the D driver of the new server, is it possible to change the path of the attachments? Or is a symbolic link the only way?



1 answer

0 votes


I would follow the path:

 4.4.4 > 5.2 > 7.0 > 7.5.2

JIRA 5.2 is a milestone release that have some changes implemented that need to be accounted for.

You could move from 5.2 to 7.0 directly.

For attachment location, there is no way to change that in JIRA 7 any more, you need to use links for that.

Windows also have the same kind of links using mklink command:

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 29, 2019 in Jira Software

Transforming Jira Software projects for general project management purposes

...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....

206 views 0 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you