Currently we are working on filtering objects based on the reporter of an issue.
What I made so far is a field with an automation that looks at the reporters name and matches this with the User field or Object Text field in Insight. This field is called Insight Employee.
Use case:
What we want to achieve now is to see in another object field all of the Inbound References connected to the Insight Employee field.
The structure of our Insight with the Inbound references is as follows:
We have an employee, for example Damian.
In a different object type called Macbooks we have objects which represents macbooks with an object attribute referencing the user Damian.
I will add an image for clarity.
On the user Damian we can see the Inbound References:
So ultimately my question is how can I see the inbound references with detail on a user described in the way above. So that when we have Damian selected in the object field on a Jira issue we will be able to see the specific device he is connected to. How do I tackle this?
IMHO and at this point it looks to me that it is impossible to get the attributes from references in your list overview. You can only get the label attribute from your outbound reference.
So sorry for the bad answer. I just could stick to "no", but let me explain my findings.
It look as if JSM asset management did not clearly separate "a view" from an "object model", as it is impossible to have views that implement inner or outerjoin linked objects and let you decide which attributes of the linked objects you want to display.
This was a very disappointing finding and I wonder what the designers were up to when creating this. It's a big loophole in the design.
in your example:
When you assign a user "Damian" to a device like a "Macbook", actually Your Macbook contains an attribute with an object type "user" (it is like a foreign key is in SQL terminology).
This is in Jira terms, considered as an outbound reference from the mackbook to the user.
Note: In the list overview of the mackbooks, it is impossible to have an extra column that supplies you with an extra attribute from the linked user, like for example "email address".
So the other way around, it is even worse:
If you get to the users object view, you will, apart from the defined attributes, not be able to define an extra column in the view that show the devices that user Damian is currently holding. Forget even about some important attributes on those devices you want to view in that user view.
JSM asset Management, forces you to click on the user 'Damian' and then click on any of the different inbound references to the devices that Damian holds, like for example the macbook.
Then click again on the pop-up to check some important attributes.
So no, no custom views possible, which under the hood implements a custom selection on inner / outer / left or right joins from multiple Object scheme's.
I hope Maybe somebody else comes with a magic solution or answer without insinuating having to alter your database schemes to fit your display or view. This often results in duplicate data linking in your schemes. that's a no no for sure... but when in need and no other options are available...
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.