Should JIRA be backed up prior to installing a new add-on?

[Thomas Hardin]

Hello all,

While, I believe this question is a bit foolish, I am asking because my organization does not have a strong background with JIRA and would feel better having more information from other experts.

They are trying to develop an Add-On evaluation process and feel that the target JIRA instance should be backed up prior to installing a new on. These are marketplace add-ons from reputable vendors. What are your thoughts?

[Nic Brough -Adaptavist- · Accepted solution]

Short answer is an unreserved yes.  Always backup before big change.

That said, I rarely do it.  I've only seen one add-on break a system badly enough to start considering going to a backup, and we should have caught that well before it was rolled out (the admin did not go through a test cycle, which really would have spotted it instantly).

I would be a bad person for saying "no, don't back up", because there's always a small chance you'll need it.  But in my experience, you probably don't need to.

[Thomas Hardin]

What was the add-on? If I may ask.

[Nic Brough -Adaptavist-]

An old Adaptavist one from before Marketplace existed - it was the Plugin Licence Manager.  You shouldn't run into it any more (I would check with Jon before saying this as accurate, but I have a feeling the need for it went away when Confluence 4 was released)

[Joe Pitt · Accepted solution]

Yes. Blessed is the Pessimist for they shall have a backup (or two)

[Satish Tatikonda]

1. Check the Compatibility of the Add-on in the new or latest or intended version quickly.

2. If it needs an update.Update it to the latest version.

3.In case it doesn't support /not compatible with the intended version then disable the add-on before going for any upgrade.Do not un-install since this may remove all the traces.

4.Later on after the upgrade enable the add-on.

Hope this helps..........

Thanks...

[Thomas Hardin]

Thank you very much for the help Gents!