User Story

As a IT director, I need the ability to create "bi-directional" object-referencing attributes to prevent my data from being out of sync.

Context

We use Assets to manage (among other things) our laptops, our users, and the relationship between the two. To visualize this, we have an object-referencing attribute on our "Laptops" object type called "Owner" linking to the "User" object type.

Problem

• When viewing the "User" objects, all we see to indicate that there's a link to another object is the "incoming reference" count, which is minimally helpful.
• Putting an object-referencing attribute on the "User" object type linking back to a "Laptop" gives me what I would expect to see (an attribute showing the laptops owned by the user), but this is an entirely different field, so there's the possibility that each side could be out of sync with the other.

Desired Behavior

When I make an object-referencing attribute in one Object Type, I have the option to add "the other side" of the reference as an attribute on the referenced Object Type.

Thus a "Owner" attribute on the "Laptop" Object Type could be tied to a corresponding attribute (which ideally I could rename as I wished, in this case to something like "Assigned Laptop(s)") which would\could only show the laptops assigned to the user.