Changes in Asset Attributes? Is this really new? What is really changing?

[Daniel Vest]

In the recent blog "Atlassian Cloud changes Mar 24 to Mar 31, 2025" there are too mentions which seem to contradict each other, but on the same note, this is something that we have been using for many months...so how it is it "Rolling out?" Is this included feature that is helpful going away? Does anyone know?

What I am referring to are the two sections: 

"The Assets object field will only display the label of an object when viewed from within the portal in Jira Service Management" & "Changes to the Assets object field when using the Jira Service Management portal".

The first says:
When you display an object in the Assets object field in Jira Service Management, you can also select one or more attributes in the User Interaction panel that will appear after the label of the object. You could use this feature to display - for example - the date the object was last modified, or the manufacturer of a piece of equipment.

These attribute values originally appeared in the search results and as part of the selected items. We will continue to show these in the search results, but this was too much detail to appear in the selected items, so now the Assets object field will only show the label when you select an item in the object picker in the portal.

This change won't affect the Assets object fields anywhere else in Jira Service Management.

While the second sounds different, in the same article:
Take the guesswork out of selecting the right Asset when filling out a form and find all attributes now visible on Asset form fields. Previously when filling out a form, customers would only be able to see the object name which made it hard to know what option to select. Now you’ll see the same attributes listed alongside each object - just like you do on request types.

The reason I question the conflicting messages of this is that we have been using, in many (proforma) forms, custom fields which link to the Asset are to display several attributes. As seen in the screenshot of the printer dropdown in the portal form.

[Trudy Claspill]

Hello @Daniel Vest 

You said you are using Proforma forms. Those are available, I thought, only in the self-hosted Jira/JSM Data Center environment. When I look up Proforma in the Atlassian Marketplace, the apps returned in the search are supported only for Data Center.

The information about changes that you are referencing applies to Jira/JSM Cloud only.

Can you confirm that you confirm which hosting type (Cloud or Data Center) you are using?

If you click on the Help button in Jira and select About, what information do you get? If you are using Data Center you should get some product version information.

[Daniel Vest]

Hello @Trudy Claspill I am certainly on Cloud. Having been a Jira user and admin for a few years in the past few positions, I am starting to like Cloud more than DC. And I have 30+ forms that I have created for use in one project alone (editing them at https://XXXXX.atlassian.net/jira/servicedesk/projects/ITNA/settings/forms) and creating custom ones is so helpful. I know for a few years they have been available in Cloud (know as Forms, forgoing the Proforma name and no longer a plugin see https://www.atlassian.com/software/jira/service-management/product-guide/tips-and-tricks/form-design-best-practices#overview) 

Connecting them with Custom Fields that link to the Jira Assets and show multiple values in the portal, combined with proper AQL in so helpful. You can combine this power of Assets, Forms, and Fields with automations and do some cool things and make faster work and lookup/edit all sorts of things. Let me know if you need me to reach out to show you some cool examples.

[Trudy Claspill]

Hello Daniel,

I am aware of the JSM Forms and Assets functionality in Cloud, though by no means am I an expert. I asked about your hosting type because you used the term Proforma, which I thought was not applicable in the Cloud environment.

I see that Atlassian used the term within their blog post, though, so I must have misunderstood.

I think the upshot of the two posts is that you will see the additional attributes in the search and pull-downs when you are looking for the object you want to select. Then, once you have selected the object, within the field you will see only the label for the object, and not all the other attributes you could see when you pulled down the field.

That is just a theory. If you want a more concrete answer I would recommend that you open a support ticket directly with Atlassian to get that information.