[OGo-Users] maybe another 64Bit bug?

[Adam Tauno Williams]

> > > I just tried to take another look into this issue, and figured out,  
> > > that I can reedit appointment notes, when I created the appointment,  
> > > but not, when someone else created the appointment for me, and I do  
> > > not have write permissions.
> > Yes, its probably this way (as long as the note is not attached to a  
> > project).
> But how should it be then? I'd say,
>  that when a user has no write access to 
> an appointment, then the user should not be able to edit notes on this 
> appointment too. Or on the other side, when he is able to create notes, he 
> should also be able to reedit notes. 
> > > Therefore I started wondering, is it intended that I am able to  
> > > create/edit notes on appointments where I do not have write  
> > > permissions to, also when I am not participating at all?

It makes sense to me that users without write access to the appointment
(but DO have *read* access) be able to create and edit notes.  I can
think of several user-cases where that would be useful/sensible.  To me
write access to the appointment regards the ability to move or delete or
change the attributes of the appointment.  If you want to prevent
notations then the best solution IMHO would be to reduce read-access. 

My question would be whether or not an appointment perceived as
"private" (no read access) can still be annotated?

> > I would say no.
> ok, created a bugreport:
> http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1939