How does your team vet new add-ons?

Question

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?

Brant Schroeder · Answer

@Cat Quinn

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.

* Justification for marketplace product, how they tested the app, examples of their testing - Submitted by the users after they test and validate in our test instance.
* Cost of the app and how will it be funded.
* How well the application is documented and link to documentation.
* Is it part of the bug bounty program.
* How many reviews does it have and overall review rating.
* How many installs does it have.
* How long has it been around.

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.