nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Show multiple attributes from a linked asset

benjamin_buchholt

Hi!

I got a requirement, to show multiple attributes from one asset on another via relation. I can only show the lable-attribute, but not the others.

As an example, I have:

locations (like stores) with name, id, latitude and longitude
devices (like handheld scanner) with name, serial number, locationId and location

I get imports for both object types where I link them based on the locationId. That works well an while viewing a device, you can see the name of the location.

Screenshot 2026-05-26 083306.png

But my (internal) client also wants to see the locations latitude and longitude when viewing a device. Is this in any way possible? If not in assets itself, maybe in a confluence list by aql?

Screenshot 2026-05-26 083448.png

In a relational database it would just be a join in a view, but JSM assets doesn't behave like a relational database

Accepted answers

Arkadiusz Wroblewski

Hello and welcome to the Community @benjamin_buchholt

Assets doesn't really work like a standard database, so it's only ever going to show the main Location label on the Device screen instead of pulling through extra fields like latitude and longitude.

Your can denormalize the data a bit. Just add "Location Latitude" and "Location Longitude" fields right onto the Device object, and let Assets automation copy those values over whenever a location is linked. It means duplicating data, but it's the easiest workaround to get everything on one screen if your Customer wish that.

Best,

Arkadiusz

Marc -Devoteam-

Hi @benjamin_buchholt

Welcome to the community.

If you are not using custom field to show this within an issue, but just in Assets, you could also.

Use attribute inheritance for child object types
Automate this action, but triggering on object creation or update and copy attribute information, you will have to use duplicate attributes.

See also this older community post: Reference-to-an-attribute-of-another-object-Jira-Assets

All comments

Arkadiusz Wroblewski

Hello and welcome to the Community @benjamin_buchholt

Assets doesn't really work like a standard database, so it's only ever going to show the main Location label on the Device screen instead of pulling through extra fields like latitude and longitude.

Best,

Arkadiusz

Marc -Devoteam-

Hi @benjamin_buchholt

Welcome to the community.

If you are not using custom field to show this within an issue, but just in Assets, you could also.

Use attribute inheritance for child object types
Automate this action, but triggering on object creation or update and copy attribute information, you will have to use duplicate attributes.

See also this older community post: Reference-to-an-attribute-of-another-object-Jira-Assets

benjamin_buchholt

Hi @Marc -Devoteam-

thanks for your ideas. Child objects an not possible in my specific setting (I simplified the example a lot) and we already tried automations. They work in general, but we reach our limit of 1000 objects per run (or so).

Since I am primarily a Java developer who is sending data to jsm assets, my first thought went like "isn't it like a database?". If in the end the requirements cannot be meet with a basic asset setup, I will communicate it to my accountants and they must live with it...

benjamin_buchholt

Hi @Arkadiusz Wroblewski

thanks for your comment. I was hoping for something like database joins but I can also understand that this is a completely different product.

I wouldn`t be happy to duplicate data, but if my accountants insist on having this "feature", maybe I need to...

I am not very familar with jsm assets, I am "just" a java developer who is sending data via imports - and I am already quite proud of being able to setup an importer with all of the settings and structure via REST. So I was just hoping that there might be another way of showing the additional data from a linked object.

Arkadiusz Wroblewski

@benjamin_buchholt

I would put it this way: the customer is king.

If the customer wants something, we need to implement it. Our responsibility is to explain clearly when a solution is not ideal and point out the possible downsides.

In the end, though, the decision is theirs.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management

assets