You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello! I am trying to standardize the process for vetting and reviewing new add-ons for Jira Software, JSM and Confluence so that we are only using what is necessary without having too many add-ons to manage. Do you have any advice for best practices on how to handle this?
We have a test instance where we allow our users to install and validate apps. We then have the following criteria that we rate the apps on. We weight the different criteria to meet our instances need.
I would suggest thinking about what will serve you the best. In the past I have had units I worked with also do a security review as part of the process to ensure that the app meets certain criteria.
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.