Skip to main content
Skip table of contents

Setting up Your Connection to Snipe-IT

This is the documentation for Snipe-IT for Jira Version 2. All Version 1 users will have to migrate to Version 2 by the end of the year.

Set up your connection to Snipe-IT in Jira. Follow our comprehensive guide for a smooth and efficient integration process.

Do you already have an installation of the asset management tool Snipe-IT? If not, you can get one here.
If yes, you can continue with the following steps to connect Snipe-IT with Jira.

  1. Make sure your Snipe-IT instance is available publicly or alternatively available for the IPs listed under Show advanced settings > Use static IP

  2. Follow these instructions to generate an API key in the Snipe-IT web interface. We suggest using a service account to generate the API key.

Required permissions and language

The account used for generating the API key needs to be a superuser, or requires at least the following Snipe-IT permissions:

  1. View permission for asset groups that should be displayed in Jira

  2. Checkout/Checkin permissions for asset groups that should be assignable via Jira

  3. View permission for Users

  4. View permissions for Categories

It is also mandatory for the account to use the English language as preferred language. This can be edited directly in Snipe-IT, under “Edit Your Profile”.

  1. Go to the configuration screen:

    • Either by clicking on the Configure button in the app listing

    • Or under Jira settings > Apps > Snipe-IT for Jira > Configuration

  2. Enter the publicly accessible URL of your Snipe-IT instance and the API key

  3. Click Save

Screenshot 2024-09-13 at 14.54.04.png

If you have a firewall on your Snipe-IT instance enable Use static IP under Show advanced settings and allowlist the IPs listed there in the firewall of your Snipe-IT instance.

The firewall should also allow the HTTP method PATCH, because some of the Snipe-IT APIs use this method to perform partial updates.


Install Snipe IT for Jira

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.