Asset Field Transition

Due to our Forge Transition, we need to change how asset data is stored within Jira custom fields.

Previously, we had to use two custom fields to link Snipe-IT assets to a Jira work item:

• An IDs custom field, which stored the asset IDs in a custom label field.

• A Titles custom field, which allowed to show linked asset titles in another custom field, e.g. when viewing work items in search results.

With our transition to Forge, we can consolidate both fields into a single Forge custom field. During the transition, it will be available as a third custom field in addition to both IDs and Titles fields and will be rolled out as follows:

• The new Forge custom field will be created and all data will be migrated automatically beginning on Sep 22, 2026. Migration should be finished by Sep 30, 2026. The new field will be able to hold both IDs and titles of assets linked to a Jira work item.

• All three fields (IDs, Titles and Forge custom fields) will be available and synced throughout October, 2026.

• The old Titles custom field will be removed beginning Nov 1, 2026. This field is read-only and we can simply remove it without any potential for data loss. The Forge custom field can be used instead, as it will show asset titles in search results and other Jira views. As this is a requirement for our app to fully migrate to Forge, we need to remove this field soon.

• The old IDs custom field will no longer be used beginning Jan 1, 2027. It is redundant with the new Forge custom field and we want to simplify the app as much as possible going forward. The custom fields will not be removed, since they could potentially be used for other data than assets and we want to avoid data loss at all costs.