Re: list of dependencies
| From contact method | Mike's Email Contact Method |
|---|---|
| Item | list of dependencies |
| Item version number | 1 |
You would need a new relationship type called TaskDependency, with two
fields: dependent (the thing that is waiting on the other task before
it can even get started), and requirement. I'm not attached to these
names, but that's the general idea of how to do many-to-many
relationships.
On Fri, Jul 8, 2011 at 11:36 AM, Todd Davies <davies@stanford.edu>; wrote:
> Todd Davies commented on Project Model Proposal
> Comment title: list of dependencies
>
> ________________________________
>
> This was Mike's idea, but I know we can't have a list as a filler of a
> field. Mike, how did you propose to represent dependencies between tasks?
fields: dependent (the thing that is waiting on the other task before
it can even get started), and requirement. I'm not attached to these
names, but that's the general idea of how to do many-to-many
relationships.
On Fri, Jul 8, 2011 at 11:36 AM, Todd Davies <davies@stanford.edu>; wrote:
> Todd Davies commented on Project Model Proposal
> Comment title: list of dependencies
>
> ________________________________
>
> This was Mike's idea, but I know we can't have a list as a filler of a
> field. Mike, how did you propose to represent dependencies between tasks?
Comment Tools
Add Comment
Hide Located Comments