Would like to know which projects are using installed add-ons

[DI2E Licensing]

We find ourselves spending more administrative time than we'd like managing add-ons.  We'd like to remove add-ons that are not being utilized.  For JIRA, Confluence, Bitbucket and Fisheye.

Does anyone know how to do this? We suspect that it's add-on specific.  But would love to hear it's not. 

Looking forward to the community feedback.

[JamieA]

Simple... turn it off, see how many people complain.

Nic gave a good example on workflow functions, but it's yet more complex. Let's say you find a function from a plugin, but it's only in inactive workflows. So does that mean that it's not used anymore, or does it mean people are working on a new workflow that will go live soon? It's all very qualitative.

[Nic Brough -Adaptavist-]

Yes, that's a better way to explain what I was getting at with defining "using", and what the questions are.

[Nic Brough -Adaptavist-]

There's really no way to do this.  You'll see some parts of it done in some other questions here, but the answers are all for a tiny fraction of the actual answers, and hence, inadequate.

The problem is that add-ons provide a wide range of different functions, and you also need to think about you define "using".

For example, if an add-on provides a field in JIRA, then usage is quite easy - look for non-empty values and list out which projects they're in.  And the next plugin provides a workflow post function, so you need to scan all your workflows to see if it's in use.  A confluence addon gives you a macro - you can search for that in the UI.  And the next one provides an export function - you'll have to ask your users if they use it at all.

So, I've just given four examples, only three of which you can code a question for, and totally different code and questions for each one.

So, yes, it is Very add-on specific. 

But... you can get a good overview by getting a list of the user-installed add-ons from the management page, exporting the system to XML and then searching it.  In JIRA, that would give you a search of all the fields and workflows in one go for example.