Add-ons, plugins and extras?

[Davet]

In this mad-cap world that is Atlassian plugins err...I mean add-ons...errr...whatever, the "Atlassian Universal Plugin Manager Plugin" is in fact not a plugin but an add-on.

You also may be forgiven for thinking that the "Atlassian Universal Plugin Manager - Plugin License Storage plugin" is a plugin but alas it is also an add-on. You can tell because it has an "Add-on key"

Something about not seeing the trees for the forest may be appropriate here!

It is just as well that Atlassian have the resources to manage this correctly or it could easily end up appearing to be amateurish.

When will it all end?

[Nic Brough [Adaptavist]]

They're in the middle of renaming "plugins" to "add ons", so it's all a bit muddled at the moment.

[William Zanchet [Atlassian]]

Hi Davet,

Yes in the new version of UPM, we have changed the word 'Plugins' to 'Add-on'. From now on we should handle as Add-on.

Cheers,

WZ

[Davet]

Your answer confirms that Atlassian does not understand the breadth of this absurdity and as a consequence has no idea how poorly this reflects on the product.

UPM stands for "Universal Plugin Manager" not "Universal Add-on Manager"

The Universal Plugin Manager (v2.9.1) by Atlassian

[Kinto Soft]

... and NEW York is a more than one hundred years old city. Everybody shoukd name it OLD York and change the name in all the maps in the World ;)

[Nic Brough [Adaptavist]]

New York is only about 350 years old, and before that, was called New Amsterdam anyway, York is getting on for 2000 (from memory, it was founded shortly before 100AD). Pablo is spot-on with his analogy. Things change. Sometimes names keep up with the changes, sometimes they don't.

[Davet]

That would be really confusing since NEW York references the original (OLD) York which still exists.

[Ellen Feaheny [AppFusions]]

You are correct in your assertions abt the term inconsistencies -

Add-on is not just an Atlassian term - is it pretty common in the industry now, and Atlassian is evolving to that logically as well.

But honestly, in product development, these types of prolifically entrenched term changes where the term is deeply seeded in legacy code, UIs, plugins, interfaces, APIs, documentation, etc. across many products - well, one of those "easier said than done".

Not always as simple as it looks to make the changes and not break or introduce bugs or instability, which is more important. Its not always *just* a label change.

I would guess that the PMs are trying to work these term changes through bit by bit with each release.

Give it time - it will work itself out in the wash.

[Matthew Cobby]

It will only end when everything is a "add-on". If you've ever looked at Stash, it's pretty much 100% "add-ons" (even if the term plugin is perhaps more appropriate for core functionality!) Ultimately, you'll pay for the functionality that you use, whether that's Atlassian or 3rd party add-ons.