happened again at issue 7369;

if it has happened with all issues which were reassigned, ... uh...

Hi Lars,
I'm not sure, whether we would like to automatically reassign
issue while changing the component - esp. if they are in state 
STARTED. Please use "Reassign issue to owner of selected 
subcomponent".

Some more general hints:
- please query for duplicates (see 2287, which is similar)
- please refrain from raising priorities to unreasonable values.
  This is no showstopper, functionality inaccessible, ... issue
- please refrain from setting the target milestone.
  It's up to developers to set this field.

For further discussion of the general guidelines I would recommend to
join the QA project (http://qa.openoffice.org) and it's main mailing
list (dev-subscribe@qa.openoffice.org).
Thanks, Stefan.

you're right (all points);

"esp. if they are in state STARTED":

then:  if STARTED don't change assignment
                  or don't let any such values be changed except by 
starter

(currently the new components group isn't informed of the new issue 
and if one didn't watch the "sent e-mail to" line and corrected the 
assignment manually no one might read the issue again, because the 
old component group might have handled it already or/and now they 
don't see it in their group anymore; as said in issue 2287, this may 
make issues nearly non-public)

imagine s.o. at Sun (you) change the component beacuse you think it 
belongs there,...

the new component owner never gets notified !   :-(

after that you must reassign it 

close