Any harm in upgrading Confluence but not JIRA?

Our JIRA is 6.1 and our Confluence is 5.2.5. Logins for AD are handled by JIRA for both and they are integrated.

We would like to upgrade our Confluence to 5.7, and JIRA afterward at a later time in a separate project.

Is this supported? Are there any gotchas? We know we will need to upgrade underlying systems on the Confluence host like Java, Tomcat, and MySQL as well as a prerequisite for the actual Confluence upgrade.

1 answer

1 accepted

1 vote
Accepted answer

Hello Joe,

Actually this would not be a problem at all! You can upgrade just one of the applications without affecting the other one. smile

However, remember that we recommend testing the upgrade process on a staging environment first, so you can check any problem that might happen, and understand how to fix and/or avoid them when upgrading the Production instance.

Please, if you have any questions on how to achieve that, let me know!

 

Best regards,

Eduardo Mallmann

Thanks Eduardo! We definitely got the staging environment built out for just this purpose. :)

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 24, 2018 in Confluence

Atlassian Research opportunity with Confluence templates

Do you use templates with Confluence? Take part in a remote 1-hr workshop. You'll receive USD $100 for your time!   We're looking for people to participate in a   remote 1-hr workshop...

1,099 views 17 14
Join discussion

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