Summary
Nowadays, users are more and more using add-ons to complement Jira functionalities, for site-admins it's tough to know if the add-ons is being widely used or if the project it was used for has been finished and thus the add-ons is not required anymore.
Suggestion
Implement an analytic for Jira admins to follow add-ons usage by endusers.
This is similar to the functionality already provided by Confluence Cloud - Macro Usage.
With such functionality as the above site-admins would be able to manage their sites bills more easily.
- is duplicated by
-
JRACLOUD-69750 Add-on Usage Statistics
- Closed
-
- Closed
- is related to
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
- Closed
-
- Gathering Interest
- was cloned as
-
- Gathering Interest
[JRACLOUD-69121] Provide analytics for third-party apps usage across Jira Cloud
+1
We would like to track the app usage in Jira, and this feature would be a great help for us in doing so.
We recently acquired another company and took over their Jira instance. This will help determine what apps are being used and what we can remove.
+1 for this feature.
Having the ability to see if we are unnecessarily granting access permissions and spending money on add-ons should be out of the box standard.
I've been asked to provide usage data for our add-ons. Essentially why are we spending this money? Does anyone use these things? Today I had to admit to my manager that I can't help.
This is absurd. Of course we should be able to have access to something related to usage. I suspect a number of these things will not be included in our next renewal simply because my contacts can provide nothing to justify the expense.
This functionality would allow us to have an overview of additional information of plugins and understand if it's still being used and doest it bring any value for a company.
This would be beneficial for our company to understand how many users (if any) use the installed apps
We would like to track app usage in Jira Cloud, and having this feature would be extremely helpful in understanding the usage patterns of our apps