Configuring Projects

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.

• Find out which version you are using

• Snipe-IT for Jira Version 1 documentation

Once you are done setting up the connection to Snipe-IT, you can configure projects individually.

1. Go to the project configuration screen:

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

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

You can configure Fields to link assets to Jira issues. Each field can contain one or multiple assets, represented by their IDs. For each field, you can also configure the categories of the assets that can be linked.

The asset fields configured do not have to be added to issue screens, and should not be directly edited by users. Once configured, they will always be shown in any issue of the project, and can be used to link assets to the issue.

In Project, you can configure the features that will be enabled on the project level. For example, showing the Assets of Reporter in a Jira issue, or adding the Asset Search page to the project menu.

If the project is a Jira Service Management (JSM) project, you can also configure in which Request Types JSM users will be able to link assets. Similar to the fields, you can define what categories of assets will be supported by each request type. The fields where JSM users can select the assets will carry the names of the fields you have added to the respective request types and will be located on the bottom of the request from.

Changing the asset field name

If the custom label field has an unsuitable name to be used on a request form, it’s possible to rename the custom field like any other custom field by going to ⚙️ Settings > Issues > Custom fields there you can search for the field you want to edit and edit by clicking the three-dots > Edit details.