I believe right now when picking a new relationship. It can either be limited to 1 list, or all lists.

I find, limiting to 1 list is too restrictive as sometimes I want to create relationships with multiple items in different lists.

But then when we select all lists... it searches through a whole lot of things that I don't need it to or sometimes I have the same name appearing in different places for different reasons.

Example,

I have 1 list for clientele, in this case let's use Clock Tower HQ. But I also have Clock Tower HQ in another list called Venues and another in a list called Referral Program.

And there are very specific details I want to be able to add for both entries. Now lets say my specific example here now is to say I've done event coverage at Clock Tower HQ, I would like to relationships to only pull from these 3 lists and NOT pull in any other of the 20 projects we've done for Clock Tower HQ in the previous years which are inside a Client Project list.

I understand many have requested to make a single relationship to a single task. But I am asking to have relationships opened to specific lists (instead of the current, one or all).

Hi there,

I created a "contacts" folder and within that folder I've created multiple lists of different types of contacts. It would be great if the "relationships" and "rollup" options would let you pick a whole folder to rollup the information. Right now, I'd have to create a column for each list in my folder to have a rollup work instead of one column pulling from a whole folder. I tried to work around this and use the "any task," but you can only relate it to a native field so that won't work.

we create one list per project in a space called "projects" using a template. clients and contacts are maintained in a separate space.

linking customers to the entire workspace deteriorates the funnel and overview.

linking customers to the projects (relationships with "tasks from a specific list") spins up many redundant relationships in the customers (relationship for project a, relationship for project b, relationship for project c, ...).

please also implement relationships with "tasks from a specific space" and "tasks from a specific folder".

I have created relationships inside each list to bind certain backlog items to product(s), where Product is a separate list of our products in a folder where I maintain portfolio artifacts.

I would like to create this relationship column at the folder or workspace level, and connect it to the same Products list. Unfortunately, the option to connect the relationship to a particular list is grayed out at this level. Nor can I add it as a column in a folder view even if I have the same column created in all lists within the folder.

[From support ticket]: The ability to have a Relationship Custom Field on List view be added at the Folder level with the information that was included on the List.

Currently, we are using folders for projects. What we wanted to achieve was pretty simple. Each folder containing the following lists:

At the folder level, a dashboard that simplifies and displays only what's needed on daily basis

We have currently two problems that are related to relationships and their level of action. At this time we cannot display or use relationships at the folder level which lead us to:

It would be helpful to be able to define list-to-list relationships from the folder, space, or workspace levels. This would automatically create the specific list-to-list relationships for all the lists in that context.

Currently, list relationships can only be made at the list level

It gives FIELD_303 Error

It would be amazing to be able to make list relationships available also at folder or space levels

Specific list relationships is great, but the gap between 'every task' in the workspace and a 'specific list' is a bit of an 'all or nothing' challenge.

-----------------

Current Option:

-----------------

---------------------

Suggestion Option:

---------------------

There is currently no way for global relationships (accessible across spaces/teams) to be limited to a specific list of tasks. Instead, users must search across all tasks, which is confusing and time consuming.