Hi Pierre,
you probably noted that somewhere, but that's what I remember from out discussion a while ago :
- When field content is changed by user, content won't change when moved. (won't inherit another value automatically)
- Pop-up to warn user when Item is moved and data will be changed, so that user can chose what will happen. (Usefull for project, etc. where one can chose what project should a task inherit the characteristics, when it has multiple project parents)
Other possibility, but problematic IMO (too many situations where this would be annoying):
- main parent data wins (when multiple parents)
Another idea involving multi-select fields type :
if at some point we get multi-select fields, what would be amazing would to be able to "cumulate inheritances" from various items.
So that a field could inherit different properties coming from different items.
e.g. :
TLItem 1 ProjectName field = Build a house
TLItem 2 ProjectName field = Swimming pool
1- SLitem a is put under TLItem1 and it inherits "Build a house" inside the ProjectName field .
2- If I look inside the ProjectName field I see : Build a house
3- Then I ctrl-drag SLitem under TLItem2 and so the ProjectName field inherits : Swimming pool
4- But now If I look in the ProjectName field I now see : Build a house;Swimming pool.
5- I now decide to remove the TLItem 1 parent link from SLitem (i.e. : It now only has one parent : TLItem 2 )
6- look in the ProjectName field of SLitem : I now see : Swimming pool
Wouldn't that be great ? if, of course, it's not incredibly taxing, performance wise.
e.g. :
TLItem 1 ProjectName field = Build a house
TLItem 2 ProjectName field = Swimming pool
1- SLitem a is put under TLItem1 and it inherits "Build a house" inside the ProjectName field .
2- If I look inside the ProjectName field I see : Build a house
3- Then I ctrl-drag SLitem under TLItem2 and so the ProjectName field inherits : Swimming pool
4- But now If I look in the ProjectName field I now see : Build a house;Swimming pool.
5- I now decide to remove the TLItem 1 parent link from SLitem (i.e. : It now only has one parent : TLItem 2 )
6- look in the ProjectName field of SLitem : I now see : Swimming pool
Wouldn't that be great ? if, of course, it's not incredibly taxing, performance wise.