Well, I suppose there are a couple of ways you could customize your way around that:
1) Make the Assignee group field default to the "default" group name, but set it so that it won't show up in menus. 2) Use workflow to set it manually after the assignment process if no qualifying assignee groups are found. Both would involve turning off some validation filters for Assignment groups, though. Rick On 10/9/07, Rabi Tripathi <[EMAIL PROTECTED]> wrote: > > That's sad. > > I had a catch-all rule, but people complained that > when they did manual autoassign using the button, the > group selection pop-up was always showing up, because > even if there was only one specific rule for that > situation...owing to the "default" rule. > > Thanks Rick. > > --- Rick Cook <[EMAIL PROTECTED]> wrote: > > > That's true, Rabi. You have to have a base group > > (i.e. Tier 1/Triage group) > > defined that can be assigned pretty much anything, > > then build your other > > groups to catch as much as possible before it > > filters down to that group. > > So in essence, that's the default group - it just > > isn't called that. > > > > Rick > > > > On 10/9/07, Rabi Tripathi <[EMAIL PROTECTED]> > > wrote: > > > > > > In ITSM 7, it looks like there's no way to specify > > a > > > default group for use when autoassignment fails to > > > find a group. > > > > > > So, if there are any gaps in autoassignment rules, > > > user is stuck, unless (s)he picks one manually. > > > > > > Can somebody confirm this is really how it is in > > 7? > > > That the ability to specify a default assignee > > group > > > (in "application settings") was thrown out in 7? > > > > > > TIA. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
