Hi,
I’ve just coded an overlay for Users.pm that doesn’t perform unique
email validation. My aim is that some users can share an email address
(mail list) so that people belonging to a team can receive all
notifications dealing with one ticket, and if the owner is out of work
place, another one people in the team can attend that request.
RT Database schema seems to allow this (email is not a primary key,
and there aren’t defined unique indexes for this record column).
Does anyone know if this is a potential damage to the structure of RT?
Can something be broken if we follow this approach?
Kind regards and thanks!
Manuel E. Cotallo.
CETA-CIEMAT, Trujillo, Spain.
I’ve just coded an overlay for Users.pm that doesn’t perform unique
email validation. My aim is that some users can share an email address
(mail list) so that people belonging to a team can receive all
notifications dealing with one ticket, and if the owner is out of work
place, another one people in the team can attend that request.
Why can’t you simply add each user (with their own email address) to a
group and add that group as an AdminCc to appropriate tickets/queues so
they get all the notifications?
RT Database schema seems to allow this (email is not a primary key,
and there aren’t defined unique indexes for this record column).
Does anyone know if this is a potential damage to the structure of RT?
Can something be broken if we follow this approach?
This is bound to break RT in horrible ways. I strongly suggest you
don’t do it.
Thomas