Assets custom fields, redesigned for scale

DATE: July 27, 2026

AUTHOR: Jira product team

RELATED ROADMAP ITEMS: Work items assets custom field

The Assets custom field has been redesigned from the ground up with a more usable interface and limits that actually match how teams work so your fields can reflect the real complexity of your work.

How it works

A cleaner, smarter selection experience

The field has been rebuilt with pagination, bulk select, and a new Quick Add option so browsing and selecting from large asset sets is fast and effortless. The updated field works consistently across create, view, update, transition, and history screens, so the experience is the same wherever you encounter it.

Room to scale: up to 200 objects per field

The old 20-object cap is gone! You can now attach up to 200 Assets objects to a single custom field on core work items & Portal screens, and view up to 50 on supporting experiences like queues, boards, and dashboards. This unlocks use cases that were previously impractical:

An engineer can attach all 150 microservices affected by a dependency upgrade in one field, in seconds
An IT lead can connect 50+ hardware assets to a provisioning request without hitting a ceiling
A program manager can tie every contract related to a vendor renewal directly to the work item tracking it

Works with automation

If you use Jira automation to create work items, the higher limits carry over. For example, a provisioning workflow can automatically attach every piece of hardware (up to 200) in a deployment to the request that triggered it.

How to get started

If your team already uses Assets custom fields on work items, you’ll see the new experience the next time you interact with one:

Open a Jira work item
Find the Assets field
Search for (or create) and add assets

For admins: No configuration changes required. All of your fields that have been configured to store multiple objects will auto scale to support the new limit. If your team has been splitting assets across multiple fields or tracking objects manually because of the 20-object cap, those workarounds are no longer necessary.

Get started with Assets

See demos of all summer releases

FAQs

Question	Answer
What were the old limits?	Previously, Assets custom fields were capped at 20 objects per field. The new limit is 200 on core work item & Portal screens and 50 on supporting views (queues, boards, dashboards).
Can the limit be increased beyond 200?	No. 200 is the new hard limit for the Assets custom field and cannot be increased further. If you believe 200 objects is insufficient for your use case, please log this feedback so the product team can consider it for future iterations.
Do I need to reconfigure my existing Assets custom fields to take advantage of this?	No. there's nothing to set up. The increased limit and the new paginated UI apply automatically to all existing Assets custom fields. Just open a work item with an Assets custom field and you'll see the updated experience straight away.
Does this work with Automation?	Yes. Automation now supports up to 200 objects in the Assets custom field, so you can automatically populate asset links when creating or updating work items.
Can I create or manage Assets schemas from a work item?	Not with this update. This improvement focuses on the experience of attaching existing Assets objects to work items. Creating and managing schemas, object types, and attributes still happens in the standalone Assets app.