Adding Suppliers to Asset Object

[Joshua Stokes]

Hello everyone,

I am wondering if there is a way (Or setting) that I can edit where, when a user creates a new object under Assets > Schemas, and adds in the Supplier, the Supplier information can be automatically populated into the Object.

See below screenshot, this example is of me creating a new Object and assigning a supplier to it, no information if populated down i.e.. Contact Name, Phone, Email etc.

Is there any way this can auto populate the information? Else we are having to type it in, over and over again.

Thanks for the help and support as always!

Cheers.

[Walter Buggenhout]

Hi @Joshua Stokes,

There's no need to do that, since you already seem to have linked the Supplier as an assets object itself to that field. Just clicking on the supplier should reveal the details of that supplier, without the need to duplicate the information into your other object. That is exactly one of the great benefits of assets.

Hope this helps! 

[Joshua Stokes]

Thanks @Walter Buggenhout  

From my understanding, I think they want it to populate the data under the 'Supplier' field (like my screenshot above) so it is visible within the Object.

I have done some further searching on this, and it doesn't look like it is going to be possible.

Hopefully some further insights from this great community!

Cheers.

[Marcel Hager]

@Joshua Stokes I was trying to do the same thing, since the last platform I was an admin/developer for this was a very easy thing to do, so you could see a referenced record's attributes directly on the form of another object type.

So far from my perspective, as a CMDB (which is what Assets is attempting to be I think) Assets and its related features are pretty poor at best, and the documentation and examples are lacking.

[Josh]

@Joshua Stokes I'm wondering if maybe this is a schema design issue rather than a feature limitation?

I'd generally recommend having the attributes of a given reference object (Supplier in this case) stored in the reference object's table. That way you have a single source of truth and only need to update it once.

With smart values and dot notation, you can still use those attributes in Jira automation. If the requirement is to see the attributes while browsing objects; clicking on the referenced object is quick and straightforward.

If the design can't be changed, you could potentially build the solution with Jira automation (again smart values would be key here).