-
Suggestion
-
Resolution: Unresolved
-
None
-
1,768
-
-
We understand how useful it would be to add attributes of a field to the form.
We are looking at addressing this work through adding support for read-only fields/attributes in forms. We are tracking work on readonly fields in this JAC issue. We don't have an estimate on when we will be able to start work on this new feature.
Currently Asset fields within Forms will only show the value of the label.
Outside of Forms we can decide which attributes to show and we want the same to happen in Forms
- duplicates
-
- Closed
- is caused by
-
- Closed
- relates to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
[JSDCLOUD-12222] Show selected attributes in Asset fields within Forms
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:
- Enables clear object differentiation,
- Increases data reliability,
- Supports the creation of complex workflows in forms, and
- 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.
, 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 - 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
I missed the box in the description talking about addressing this with read-only fields. This won't work. Users need to see the attributes in the dropdown so they can select the right option. Just make it show up as text. If I have an object named Printer 2 and it has a location of 4th floor let it show in the dropdown as "Printer 2 - 4th floor" or "Printer 2 (4th floor)".
If I want to show the printer name, location and status it could look like "Printer 2 - 4th floor - Available" or "Printer 2 (4th floor - Available)"
96677a1d9b4c Is there an update? October 2023 has come and gone and June 2024 is in 3 days😬
This feature would be hugely impactful for my team as it would allow us to use forms (with conditional logic) to display the attributes of assets within the portal. For example, I'd like to show my customers a list of devices we store for them so they can choose the correct one from a dropdown list, but we want the customer to see the device's serial number, RAM, hard drive space, condition, etc. so they can make the correct choice when filling out the form. Forms are so important because they provide conditional logic so it would be great if we can get some additional improvements for feature parity with the traditional method of creating request forms.
Went to build a form using an Asset field today, specifically because I wanted attributes to show up with the selection so users could be sure they're picking the right option. It is very weird from a user's point of view that the search still keys off the attributes that aren't being shown, and makes it look like the results are incorrect.
Hello,
Can we please get this fix asap, there are several forms impeding us to properly serve our customers, due to the lack of development on this fields. It is impossible to work in native form as not all the function of proforma exist, it is also very inefficient to try to create blended forms, please bring the solution to live soon!
Thanks,
Eunice
Can anyone give an update on the status adding the Insight/Asset field capability in ProForma/Forms within JSM DataCenter? We would like to make use of this feature.
Looking forward to this. Our goal using this feature would be to replicate our current equipment sheet which not only contain the Name (label) of the device but also serial number/model, etc
Also the fact that the devices are onyl showing as a multi-choice selector is a little light. We could use the ability to format is a multiple fields type like a table :
Name / Serial / Model / Value
Object #1 xxxx/xxxx/xxxx/xxxx
Object #2xxxxx /xxxx/xxxx/xxxx
...
That we we can send a clear list of equipment to a user so that he can then consent and sign it.
Could you please consider in the same roadmap the JSDCLOUD-12091 Assets field does not display all search results on the portal - Create and track feature requests for Atlassian products. ? thanks
We are considering this work as part of our roadmap for FY24 (July 2023 to June 2024). We will provide another update by October 2023 on our plans.
Thanks,
Simon
JSM Principal Product Manager
We understand how useful it would be to add attributes of a field to the form.
We are looking at addressing this work through adding support for read-only fields/attributes in forms. We are tracking work on readonly fields in this JAC issue. We don't have an estimate on when we will be able to start work on this new feature.
This should be added as fast as possible. A lot of clients I work with want more than just the name. Use case encountered today : Show the department's code and the department's name. For now, I need to create a new object type and concatenate the two attributes into the name of my new object type ... Not optimal at all.
It is actually worthless to have this field on form, if we are not able to display needed attributes. This is actually the reason we are adding them to the form..
Please do consider this option as it will really cement the use of Forms/Assets for us.
We are working on implementing this feature, soon we will start the rollout.