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.

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.

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 would be so effective to have a relationship field be able to link 2-way. This would allow a seamless relationship between two tasks under the same relationship type. Right now, we can add the same relationship custom field into two different locations, however, when adding a relationship, from one task into another, where you add the relationship will sit in that custom relationship field, but in the linked task, it'll show as "Reference". If the same custom field relationship is in each list, and two tasks are added with a relationship together, my thoughts are we should have the ability to show it as a two-way relationship. Organizationally, this would be exceptional.

Just as with Docs and other Tasks, if you create an asset that a Task needs relate to. With Forms (and Whiteboards) you have to mess around finding, copying, and pasting links. It seems sensible to be able to relate out to them in a common way.

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).

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.

When we end up with duplicate tasks for the same development, we need to make sure that all the task links and related items of the duplicate case get applied to the "live" case, so that we can properly track all the customer requests and dependencies

In a rollup for a relationship that is for any task in the workspace, I'd like to be able to have the option to rollup the task type.

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.