Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Confused about dependencies in Assets

Ste404
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 22, 2024

Hi there,

I have a people schema in assets and a hardware one.  The Owner in Hardware is a object referencing a person in People.

When I put in a ticket though for this person, even if it is a ticket where the hardware item is not selected if I go into the graph view in assets, click on the hardware asset for a person all the issues for that person appear as linked issues.

I get if I am in the people graph I would see all the linked issues where that person is the reporter, but I thought in the hardware item in that schema I would only see issues where that hardware was a selected item from an assets field.

Should I be using a particular 'Additional Value' for the Object that is linking back to People?

Is there a way to turn off the 'Linked issues' in a schema in Assets.

1 answer

1 accepted

0 votes
Answer accepted
Eugenio Onofre
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 23, 2024

Hi @Ste404

When all issues related to a person are displayed in the graph view of a hardware asset, it's likely due to how the Asset-Object-Link is configured.

In your setup, since the Owner in the Hardware schema is an object referencing a person in the People schema, any issue involving that person, irrespective of the specific hardware item, might be shown in the graph view. This is because the link is between the person and the hardware, so any issue involving the person could be interpreted as relevant to the hardware.

To ensure that only issues where the hardware item is specifically referenced appear in the graph view, consider the following:

  1. Asset Field in Issues: Make sure you are using an Asset field in your issues to reference the specific hardware item.
  2. Configure Asset Field: Ensure the Asset field is correctly configured to reference items from the Hardware schema.
  3. Filtering: When setting up views or reports, use filters to specifically target issues where the hardware asset is mentioned.
  4. Review Asset-Object-Link Configuration: Check the configuration of the link between the Hardware and People schemas. You might need to adjust the settings to ensure it's only displaying issues directly related to the hardware item, not just any issue involving the asset's owner.
  5. Additional Values: The 'Additional Value' for the Object linking back to People may need to be adjusted based on your requirements. This might involve setting up more specific object attributes or references that better define the relationship between the hardware and the issues.

Please remember to accept this answer in case it helps you resolve your question as it may also help other community members in the future.

Regards,
Eugenio

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events