1 and 2 - check the audit logs, the admin audit may have it, and the add-on audit log definitely will
3, 4 and 5 - that's pretty much impossible for add-ons. You need a different strategy for each type of add-on.
Add-ons are installed globally and add all sorts of functions. For some add-ons, you could try trawling access logs (if you have them) to see if users are hitting the urls it provides, but even that wouldn't give you any answer for projects. If the add-on provides a workflow function, you could look through all the workflows to work out where it's been used, then look at which projects use that workflow and then the users with permission to perform that transition and hence get users too, followed by looking at all the issue history to find out when the transition was executed. And for an add-on that does diagrams, look at attachments. And for an add-on that... Well, you see the point - there's no way to just say "last used/users/projects" for add-ons in general
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs