Confluence UPM 2.9.0 Upgrade

[Davet]

Just tried the upgrade from UPM 2.8.2 to 2.9 in the lab

The upgrade seemed to complete without errors but then Balsamiq lost it's license and "System Add-Ons" diappeared.

Refreshed the database and files from production, ran the upgrade again and same result.

Can anyone else confirm this please?

[ChangJoon Lee · Accepted solution]

System Add-ons are no longer visible by default.

Now, you can choose it from following for options on your filter.

"Action Required"

"Paid via Atlassian"

"User-installed"

"System"

Once you select a filter, it will show its list of plugins.

[Davet]

Thanks for the prompt and correct reponse.

Perhaps you would also know when the UPM transitioned from being a system plugin to a user-installed plugin?

I am assuming that the Balsamiq mockup has a problem with the new UPM and now refuses to recognise the attached license.

[ChangJoon Lee]

UPM always comes with Atlassian product, if you didn't update it, it stays as System plug-in.

It moves to "User installed" once you update it.

If Balsamiq worked with 2.8.2, probably downgrade to 2.8.2 will be the best option for you.

Cheers.

[Davet]

Hmmm...interesting take on the definition of "User-installed"

Confluence 4.x defines user installed like so:

User-installed Add-ons

These add-ons may be configured, enabled, disabled or uninstalled.

I would think that the choice of these options on UPM would have problematic and unintended consequences.

p.s. There are plenty of other "System Add-ons" that do not get reclassified in this way after user selected upgrade!