[quote=Tom]

This appears to be a bug:

 

Ctrl+Drag a TLI to become a sub-item of another TLI

Select the item (in it's new sub-item location)

Alt+Left-Arrow to move it back up (I know it's not logical but that's not the point - I had actually dragged it under the wrong item and just did this without thinking, planning to move it under the next item)

Refresh grid - the item has disappeared completely from the grid

 

 

When I tried it in clean install, it happened as reported above

When I tried this in a 'TEST' grid in my usual file/install and all the items in the grid disappeared on refresh! I'll have to look closer at that & try figure out whats going on there...

 

 

[/quote]

 

 

Yes, I was able to reproduce this.

 

I think there are 2 bugs. What happens :

 

1- when you ctrl-drag/drop a TLI under another item (which has the effect of creating a new  link to a parent) IQ will behave as if you just moved the item : source field will be un-assigned  from the item -- which shouldn't IMO since "ctrl" was held and item is still also a TLI.

 

2- then when you move back the item as a TLI, it doesn't get its "source field" reassigned. This also shouldn't happen...

 

 

Pierre : there are a few other instances of weird field autoassigment misbehaviour mentioned in Mantis (I'm the reporter...). These are pretty annoying as they happen invisibly (unless your eyes are constantly on the properties pane) and these make it easy to "lose" items in the process : a pretty bad problem if you're dealing with tasks, events, projects, etc. Who wants to have tasks disappear from a list because of field auto-assignment/auto-unassignment misbehaviour?

 

These have been a problem for many months now. (Unless some have been fixed without notice. I'll check that out tonight.)