Feature Requests

[From Blue Whale] I would like to be able to add relationships in bulk, especially by adding a folder or list. This would particularly be useful for dependencies.

Many of our major projects appear as spaces or folders, not tasks. Being able to connect a doc to an overarching project instead of a task would be useful.

I develop websites and when I sign a new client, I make an entire folder for the project and then have lists for each step of the project underneath. I keep track of all clients in a completely separate list so i know costs, status, contact info, etc. Can we have the ability to link folders and lists to tasks? And not just being able to link tasks?

I wish there was a way to add relationship as a custom field for form entry. Example: We use the system as an event management system, and sometimes we have obscure requests that apply to a specific event. We would like to be able to submit a form with the obscure request, but tie it to a relationship (event from list).

Here's a sample use case: I want to create a list of projects and group them by Client. The Client is a relationship to a task in a list called Clients. For some reason, I do have the ability to group by some of the linked items, like assignee (in this case I called it "Client Owner").

It doesn't seem there is a way to add the values for a rollup field. It would be great to be able to use rollup field values from relationships in formula fields.

Currently, when creating a custom relationships, it is only possible to link a task to another using the relationship from one of the tasks. It would be great if you enabled the ability to create relationships which work similarly to dependencies. In dependencies, the relationship name indicates how each task relates to the other (blocking or waiting on), and the same should apply to custom relationships. So if there is a task that represents a customer, and a relationship that represents that the task is for that customer, than it should be possible to create the relationship both from the task related to the customer and from the task representing the customer itself. Each direction will have its own name. In our example it will be something like "Related Customer" and "Reelated Tasks". I do not see much use for custom relationships without this feature, as the current state does not capture any aspect of the nature of relationships (one aspect is relationships being bidirectional).

Currently, if you have a relationship created by using the option 'task from a specific List', this relationship will disappear if you move the task to another List or duplicate the task. Allow these List to List relationships to be maintained when the task is moved or duplicated.

Relationships nowadays just allow to select tasks previously created. It would be nice if we coud add a new task directly on related list through Relationships.