[OGo-Users] Conflict Detection (Bug?)

[Adam Tauno Williams]

--=-DdnaOO2JEE64/B72MKxS
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I have user A who is member of team X.

I create an appointment with a participant of X and a role of
NON-PARTICIPANT.

I create an overlapping appointment with a participant of A and a role
of REQ-PARTICIPANT.

I see a conflict.

Is this a bug?  My understanding was that a role of NON-PARTICIPANT
would suppress conflict.

Oddly the appointment with user "A" does not show any conflict,  but if
I look at the appointment with the NON-PARTICIPANT team as a participant
I see a conflict with the user-A appointment.

The same is true if I create an appointment with A:NON-PARTICIPANT and
another overlapping appointment with A:REQ-PARTICIPANT.  The
NON-PARTICIPANT appointment sees a conflict with the REQ-PARTICIPANT
appointment but the REQ-PARTICIPANT does not see a conflict with the
NON-PARTICIPANT appointment.

Shouldn't conflicts always appear from both sides?

My understanding of conflicts is from the map:
Conflict-Map as implemented in the conflicts command:
              CHAIR REQ-PART OPT-PART NON-PART <NULL>
NEEDS-ACTION  yes   yes      might    no       yes
<NULL>        yes   yes      might    no       yes
ACCEPTED      yes   yes      yes      no       yes
DECLINED      no    no       no       no       no
TENTATIVE     yes   yes      yes      no       yes
DELEGATED     no    no       no       no       no

--=-DdnaOO2JEE64/B72MKxS
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBG8XLzLRePpNle04MRAh+tAJ9Ky7Ef9VWdJZJPf4ecced9iyGd5gCdGm0a
XaKJglSgO29c9G052SVfrrk=
=/xtN
-----END PGP SIGNATURE-----

--=-DdnaOO2JEE64/B72MKxS--