[rt-users] group not found

[Kenneth Crocker]

Alan,


	I have run into the "Requestorless" tickets before and found that it 
only happens when I use the "Quick Ticket" function at the bottom of the 
home page. I mentioned this to Jesse over a year ago and my 
understanding was that it was addressed in 3.6.3. As to the no GroupID 
stuff, are the tickets in the same Queue? Perhaps the group has 
privileges in one Queue and not the other? Just a thought.

Kenn
LBNL

Alison Downie wrote:
> 
> 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.
> 
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy 
> a copy at http://rtbook.bestpractical.com
>