Here's something I've been sitting with: few months back someone asked me to pull a report on our Jira app usage and I realized, I have no idea what's actually being used in my org. We're paying for apps that might be gathering dust and I can't even tell which ones.
I dug around and found ECO-470 on Atlassian's feedback board (383 votes, open for over 4 years, Four years!). That's when I knew this wasn't just my problem.
So I've been exploring building a Forge app to solve it for myself first, honestly. Not because I think there's a market opportunity (though clearly there is), but because every Jira admin I talk to has the same story. We're all hacking together workarounds, emailing vendors, squinting at audit logs.
What are you all doing today to track app usage? I feel like we're all figuring this out the hard way. Would love to hear your approaches, even the messy ones.
Also interesting that Jira already had this on DC but cloud doesnt for some reason?
@David Day_ Appcento I think this would be a very good topic to discuss in the Marketplace App group. 😉
Best,
Fadoua
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Tracking will depend on the app. There is no 100% safe and easy way to do it.
Some apps are used in workflows, create new tabs, they work on a work item, etc.
So the tracking ATM will be per app.
For example, Script runner. It comes with a way to check the Behaviors running and the scripts globally. Anything running in a workflow, you will have to check the app KEY and see if its being used.
Same with JMWE. app key, API to check the workflow.
For other apps, check the vendor support page or ask them directly how to. They should have a way to.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
makes sense that tracking is app-specific right now. If every vendor has their own way, there's no single pane of glass for admins like me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One thing I'd add is that "used" doesn't always mean "valuable." Some Marketplace apps are only touched by a handful of admins but are absolutely business-critical (think workflow extensions, automation, or security apps), while others may have lots of clicks but little real impact.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
great point about "used" vs "valuable.", important distinction that any tool would need to account for. Not all usage is equal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This capability gap is tracked under ECO-985, ECO-315, and CLOUD-12134. Keep in mind that the App Usage for Jira feature often mentioned in these discussions is strictly for Data Center, not Cloud.
Because billing user counts and background API traffic don't reflect actual human adoption, the most reliable is to build an internal governance routine.
You'll want to ask vendors directly if their specific apps offer internal analytics, audit the app's configuration footprint (active fields, workflows, or scripts), and require regular usage validation from a designated business owner. Always review the vendor's data-retention rules and test in a sandbox before officially pulling the plug.
Best,
Arek 🤠
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks for pointing to these threads. I'll be following those. And your governance routine suggestion is solid, but it shouldn't have to be this manual in 2026.
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.