Researching on the plug-in usage by our project teams.
Evaluating whether to Enable the Plug-in or to Disable the existing plug-in after the Upgrade to JIRA Data Center 7.9.1 version.
Currently we are using JIRA v7.3.9
You have to look at what each plugin does, and how you have configured it.
There is no easy way to link plugin usage to a project. Plugins can provide all sorts of things - fields, reports, gadgets, workflow functions, project templates, timesheets, ui changes, scripting, etc etc etc.
The only useful approach is to work through what you have manually. Although there is a quick and dirty trick - turn the plugin off and see who screams (only recommended when you really cannot be sure that someone is not using it)
I wanted to know the count of projects,users,workflows,schemes,boards the plugin is used.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same answer - go through your config and count.
Let's take some cases to show you why you can't do it.
1. I once wrote an add-on that reported on some numbers in projects. It was a report that appeared in the project report area. All projects could use it. How do you define "usage"? It's in all the projects, anyone who could see a project could use it. The only good definition of "used" here is probably "people ARE clicking on it". Which you can only measure by reading the access logs on the proxy server.
2. An add-on provides a gadget. The usage count there is "on the dashboard of an active user"
3. An add-on provides a workflow function. Easier to count in theory, but you'll still need to read every workflow to see if the function is used, then read the workflow schemes and then work out which project they are associated with.
Now imagine a plugin that provides more of a service suite than a single function - I can think of nine add-ons that provide many modules of all three above and a load more, without even glancing at the marketplace.
So, as you can see, you simply cannot "count where plugin is used" without analysing what the plugin does and deciding for *every* module in a plugin, what the rule that defines "used" is.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.