Lauren Lightle-Watson
We are utilizing custom field relationships to associate all work across spaces and teams with our clients. Example: Client A has 3 projects in Implementation, 7 issues in Support, and 3 items in Engineering/Development that are all visible in Client A's record(task). We currently have 72 relationship custom fields, and the number keeps growing. We are running into some issues navigating these and have concerns with maintaining these relationships. We would like to request the following items be considered:
  • The use of the same relationship field across lists. We would like to build a single client relationship field that can be added to multiple spaces and lists to connect items back to the client's record instead of having to create unique relationship fields for each list. This would reduce the number of duplicate 'client' fields.
  • Currently, task cards display all relationships at a glance. When you click on one relationship type, it opens the Related tab. It would be better if when you clicked on the relationship, it not only opened the related tab, but also went directly to the corresponding section in the related tab. For example, if I click on the 25 Client Contacts link under Relationships, it would open to the Client Contacts section on the Related Tab regardless of its relationship order. This would help us tremendously as it eliminates our need to scroll through a large amount of empty sections in the Related Tab to locate the existing relationship.
  • Better yet, if we could have the ability to filter the Related Tab in tasks down to only those sections where a relationship exists, we could more easily navigate our relationships.