🔜 Coming Soon: Improved Behavior for Assets Custom Field in the Portal

[#1]

Hello Team,

I’m Mohamed, one of the product managers in the Assets team.

We’re excited to share an update about an upcoming change to the behavior of the Assets custom field in the portal, which aims to address feedback we’ve received from many of you.

What’s the issue?

Currently, when a user selects an object in the Assets custom field on the portal, we concatenate all searchable attributes. However, it differs from how the field behaves in the issue view, where only the label is shown once an item is selected. Furthermore, when a user views an object linked to an issue on the portal, only the object's label is visible. At present, users have no ability to customize or modify to choose which attributes to display.

This inconsistency has led to challenges:

• Difficulty identifying selected items: Users struggle to read and identify objects they’ve selected, especially when there are many searchable attributes.
• Confusion between portal and issue view behaviors: Users are unclear why the field behaves differently in different screens.

Issue View

Current Portal View

What’s changing?

To improve consistency and usability, we’re introducing a couple of changes:

• We are updating the portal behavior to show only the label once an item is selected—matching how it appears in the issue view.

• We are introducing a new setting for the custom field that allows you to control the display options on the portal issue view, similar to the existing issue view.

We are believe these changes will provide the following benefits:

• Provide a cleaner and more intuitive experience for users selecting objects.
• Reduce confusion caused by mismatched behavior across the portal and issue view.
• Empower customers with the flexibility to customize and display various types of information tailored for portal users.

When will this happen?

We are currently implementing these changes and, while we do not have an estimated time for the release yet, we wanted to share this update as early as possible. This will allow you ample time to plan any necessary adjustments and provide feedback.

What if there’s an issue?

We’re confident this update will enhance the user experience, but if you encounter any issues, please don’t hesitate to reach out to me directly at mhassan@atlassian.com or contact us through the regular support channels.

We look forward to hearing your feedback and thank you for helping us make Assets better for everyone!

Thanks,,
Mohamed Hassan
Product Manager, JSM Assets Team

[Iman Attia]

It would be great if this also applied to the the asset fields on the forms attached to the portal request type too!

[Mohamed Hassan]

Thanks for the feedback @Iman Attia at this stage we are limiting the changes to the main issue view/portal view but we will definitely keep this in mind for future improvement to Assets in forms.

[Eglė Kaziulionytė]

https://jira.atlassian.com/browse/JSDCLOUD-12222 - this should be definitely addressed all together. I do not see it as "improvement" - it is simply a bug, because it behaves differently than it is setup in configuration.