AW: too much requestors

and where are these values stored in the database?

Bauer, Felix wrote:

Hi,

I’m atm a bit confused. If I create a new ticket RT adds another
person

to the requestors.
Ok, I’ve got a bug somewhere but I can’t find it. For better
understanding, I’d like to know
where I can see “Who is a requestor of this ticket”… sorry for the
noobish question, but I’m
not working all the time on RT and need some time to get into it and
I

Bauer, Felix wrote:

and where are these values stored in the database?
You don’t need it.

Each ticket has special groups(4) for users who play roles against this
ticket.
Table Groups field Domain eq 'RT::Ticket-Role’
Role stored into field ‘Type’:

select distinct Domain, Type from Groups order by Domain, Type;
| Domain | Type |
| ACLEquivalence | UserEquiv |
| RT::Queue-Role | AdminCc |
| RT::Queue-Role | Cc |
| RT::Queue-Role | Owner |
| RT::Queue-Role | Requestor |
| RT::System-Role | AdminCc |
| RT::System-Role | Cc |
| RT::System-Role | Owner |
| RT::System-Role | Requestor |
| RT::Ticket-Role | AdminCc |
| RT::Ticket-Role | Cc |
| RT::Ticket-Role | Owner |
| RT::Ticket-Role | Requestor |
| SystemInternal | Everyone |
| SystemInternal | Privileged |
| SystemInternal | Unprivileged |
| UserDefined | |

Look into archives, I described allready other stuffs about User and
Groups tables.

ALSO I did said why anybody should use DB directly and use RT API instead.

		Good luck. Ruslan.