[rt-users] group not found

[Alison Downie]

I must admit it does seem strange that the ticket is able to be 
'requestor-less'! I wish I could make sense of the intricacies of RT a bit 
better but I can only assume that at the point of changing the Requestor 
name, it removed the old one successfully then didn't complain too much 
that it didn't recognise the new requestor (that probably had a typo). Now 
that we have spotted the mistake and are trying to correct it, it's 
complaining bitterly! 
Anyway, I can change the Requestor on another ticket to the Requestor that 
we are trying to allocate to the rogue ticket in question so the Requestor 
that we are trying assign would appear to have a valid groupID :-)

Thanks for your comments, though - at least my train of thought isn't too 
far off the mark!!

Alison

On Thu, 29 Mar 2007, Alan Brault wrote:

> Alison:
>
> That could be the case, though what looks like is happening is whatever
> watcher you're assigning doesn't seem like they have a groupID at all
> though that could just be a fluke given the ticket doesn't have a
> requestor which is odd because RT shouldn't allow that to happen in the
> first place as far as I know.