ist@ARSLIST.ORG
Subject: Re: Incident Mgmt 7: No default Assignee Group?
**
Which is why I would either attack it on the front end and then bypass
the functionality entirely, or wait until it's done and use the
qualifications that now generate an error msg to generate a "default&qu
on list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of strauss
Sent: Saturday, October 13, 2007 2:34 PM
To: arslist@ARSLIST.ORG
Subject: Re: Incident Mgmt 7: No default Assignee Group?
**
I know what you mean - and I was thinking that setting default values in
those three fields would result in aut
Subject: Re: Incident Mgmt 7: No default Assignee Group?
**
Chris, setting the Assignee Group fields isn't something I will suggest,
because I have neither tried it nor really thought through how that
would affect the functionality of the module. I do understand how your
support organization stru
in the base HPD:Help Desk).
Chris
_
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of strauss
Sent: Saturday, October 13, 2007 4:06 PM
To: arslist@ARSLIST.ORG
Subject: Re: Incident Mgmt 7: No default Assignee Group?
**
Rick, are you suggesting s
not to mess
too much with what's in between.
Rick
_
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of strauss
Sent: Saturday, October 13, 2007 2:06 PM
To: arslist@ARSLIST.ORG
Subject: Re: Incident Mgmt 7: No default Assignee Group?
**
So
mailto:[EMAIL PROTECTED] On Behalf Of Rabi Tripathi
Sent: Thursday, October 11, 2007 3:53 PM
To: arslist@ARSLIST.ORG
Subject: Re: Incident Mgmt 7: No default Assignee Group?
**
For now, I am going to tell them that this default group will show up in
their list. I will consider code change late
For now, I am going to tell them that this default group will show up in their
list. I will consider code change later. Thanks.
- Original Message
From: Rick Cook <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Tuesday, October 9, 2007 4:24:46 PM
Subject: Re: Incident Mgmt
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 group
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
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
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
11 matches
Mail list logo
