Assets custom field scalability

The Assets object custom field connects Assets objects to your Jira work items. You add it like any other field, point it at an object schema, and then people can select objects on a work item, in a request, or on the portal. This page explains how the field behaves at scale - how many objects it can hold, where it is supported, and what to watch for as your data grows.

How many objects a field can hold

A single Assets object custom field can store up to 200 objects. To let a field hold more than one object, turn on Field can store multiple objects in the field configuration; without it, the field holds a single object.

Where the field is supported

You can add the Assets object custom field to work items in Jira and in Jira Service Management spaces. In Jira Service Management, you can also add it to request types and show it on the portal, so customers can select objects in their requests. When the field is added to a request type, portal customers are automatically given the view-only User role.

To create or edit Assets object custom fields, you need a Jira license.

Scoping a field to the right objects

Each field is scoped to one object schema. You can narrow what it shows with an AQL query in Filter scope (AQL), and filter against values from other fields with Filter work scope (AQL). Note that placeholders can’t be used in the Filter scope (AQL) field.

How object visibility can vary

Object visibility can differ across experiences. Most experiences - creating, viewing, or updating work items, and the portal view in Jira Service Management - display the full list of up to 200 objects. If you rely on the field in an integration or a less common surface, confirm how many objects it returns there before you depend on it.

Before you hit a limit

If a field needs to reference more than 200 objects, that usually points to a modelling choice rather than a display setting. Consider scoping the field with AQL so it only offers the objects that are relevant to that work item, splitting a broad object type into more specific ones, or linking related objects through references instead of listing them all in one field.