We are working on implementing this feature, soon we will start the rollout.

We are interested in seeing this improvement to Assets custom field rendering in Forms.

Please provide a status update when possible.

96677a1d9b4c  please take this into considerations

Problem Description

Currently, Jira Cloud Assets lacks the functionality to display selected attributes of an asset object within forms. Instead, only default values (such as object names) are shown, making it difficult for users to accurately identify and select objects. This limitation poses challenges, particularly in environments with complex data structures, extensive asset repositories, and enterprise-level operations.

Reasons Why This Feature Is Valuable:

1. Improved Differentiation of Objects

• Challenge: In many cases, multiple objects have similar or identical names (e.g., devices, users, systems). Without additional attributes such as serial numbers, locations, or specific statuses, identifying the correct object becomes nearly impossible.
• Solution with the Feature: Displaying selected attributes (e.g., inventory numbers, location, or status) allows users to clearly distinguish between objects, improving accuracy and efficiency when selecting assets.

2. Enhanced Data Reliability

• Challenge: Without visibility into key attributes, users are prone to misassigning assets, which can lead to incorrect approvals, maintenance requests, or allocations.
• Solution with the Feature:
  • Showing relevant attributes in forms ensures users can reliably select the correct asset.
  • Reduces the risk of errors and their consequences, such as incorrect escalations or flawed reporting.
  • Maintains a consistent and trustworthy data repository.

3. Support for Complex Processes in Forms

• Challenge: Large organizations often require dynamic and context-aware forms to handle complex workflows, such as approvals, change requests, or asset management. Without relevant attribute visibility, it is difficult to design forms that cater to such needs.
• Solution with the Feature:
  • Forms can be tailored to display attributes based on specific contexts, such as department, location, or asset type.
  • Facilitates workflows like maintenance scheduling, resource allocation, or IT asset tracking, making them smoother and more reliable.

4. Meeting Enterprise Requirements

• Challenge: Enterprise-level organizations often manage vast numbers of assets with extensive metadata. Without the ability to display relevant attributes directly within forms, the Asset module becomes severely limited in usability for such companies.
• Solution with the Feature:
  • Enterprises can manage assets more effectively by highlighting critical attributes in forms.
  • Improves scalability and adoption of the Jira Asset module, making it a more attractive solution for large organizations.

Summary

The development of the feature "Show selected attributes in Asset fields within Forms" is a crucial enhancement that:

1. Enables clear object differentiation,
2. Increases data reliability,
3. Supports the creation of complex workflows in forms, and
4. Aligns the Asset module with the needs of enterprise-level companies.

Implementing this functionality would significantly improve the usability, scalability, and overall value of Jira Cloud Assets, particularly in data-intensive and enterprise environments.

Happy new year , Any update ?

Hi -

The Assets field in the form needs to follow the config of the Assets custom field that it's linked to.

Example:

Users - using only the Name of the object can be confusing, with multiple John Doe users listed and no real way to distinguish between them.  Having the email (john.a.doe@atlassian.net, john.b.doe@atlassian.net) show as well, as we are trying to do, gives unique options.

Thanks.

96677a1d9b4c , do you have a update on this issue?

96677a1d9b4c - this is great news!

I just wanted to clarify if the intent is still to deliver this via read only fields elsewhere on the form per the description, or if you're going to look into[ what I asked for|https://jira.atlassian.com/browse/JSDCLOUD-12222?focusedId=3458395&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3458395] and have the attributes show in the dropdown like they do elsewhere in Jira? Happy to discuss my use case at any point if that would be helpful.

Hi everyone - a quick note to say that we have tentatively added this to our roadmap in the next 6-12 months. While we don't have exact dates yet, we understand its importance and will keep you updated on our progress.

Thanks,

Sam

JSM Principal Product Manager

Hi, 

Any updates here?
 

Any updates here?