Record links for to-do

What is the challenge?

Conceptually, a to-do on a feature having a record link is no different from a requirement on a feature having a record link.

The to-do could be blocked by or block any other record, it could depend on or be depended on.

Several teams have started using to-dos more frequently and want to track these relationships directly on the to-do instead of to the parent record.

For example, one team uses to-dos to track the dates when a feature should pass through its various statuses (because we cannot allocate expected dates to statuses). They would like to show a dependency between the design stage to-do and a future feature. When feature one completes design, the next feature can start on design.

A different team wants to track non-product activity like legal sign off as to-dos. This sign-off is the specific dependency for starting other work. It is too generic to say the feature to which the to-do belongs is the dependency.

What is the impact?

Workflows can be managed effectively.

Describe your idea

Add record links to to-dos.