I agree with Tauf.   It sounds like your assignee's are fulfilling the change 
manager role, so configure them as such.   You have numerous options for 
setting up management as approvers w/o having them interact with the 
application.   Either based on assignee like Tauf suggests or individual or 
group approvers based on other criteria.
 
-- 
Chris Danaceau
AttivaSoft Solutions Architect

________________________________

From: Action Request System discussion list(ARSList) on behalf of Chowdhury, 
Tauf
Sent: Wed 4/15/2009 2:04 PM
To: [email protected]
Subject: Re: Change Manager Role in Change Management 7


** 

>From reading through what you are doing at a high level, I would configure it 
>as such:

Give your "assignees" the Change Manager Role. Make the testers the Change 
Assignee. Then configure your Approval Mappings that sends an approval to the 
Change Assignee group.

 

What you are doing would work too but I would be concerned about reporting 
metrics and things so that is something to think about if you haven't done so 
already.

 

Tauf Chowdhury 

Analyst, Service Management

Office: 631.858.7765

Mobile:646.483.2779

 

 

 

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Pierson, Shawn
Sent: Wednesday, April 15, 2009 1:51 PM
To: [email protected]
Subject: Change Manager Role in Change Management 7

 

** 

Good afternoon,

 

I've been thinking about using the Change Manager role on Change Management to 
reflect testers for changes rather than listing the manager of the group making 
the change.  The reason is because at this point, the person that actually 
"manages" the schedule and verifies that that tasks are completed are the 
Assignees, and most I.T. management prefer to do approvals and use reports 
rather than interact directly with the Change application.

 

So, what I am thinking of doing is setting up all of the potential testing 
approvers as Change Managers so that going forward, the Assignee can pick one 
of them, and we do an ad hoc approval before implementation that picks up the 
Change Manager to do the approval.

 

Can anyone see any down side to using the Change Manager field in this way?  Is 
there a better way to have people performing the UAT do a sign-off in change 
management?

 

Thanks,

 

Shawn Pierson 

Remedy Developer | Southern Union

 

 

Private and confidential as detailed here 
<http://www.sug.com/disclaimers/default.htm#Mail> . If you cannot access 
hyperlink, please e-mail sender. 

_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ 

________________________________

This e-mail and its attachments may contain Forest Laboratories, Inc. 
proprietary information that is privileged, confidential or subject to 
copyright belonging to Forest Laboratories, Inc. This e-mail is intended solely 
for the use of the individual or entity to which it is addressed. If you are 
not the intended recipient of this e-mail, or the employee or agent responsible 
for delivering this e-mail to the intended recipient, you are hereby notified 
that any dissemination, distribution, copying or action taken in relation to 
the contents of and attachments to this e-mail is strictly prohibited and may 
be unlawful. If you have received this e-mail in error, please notify the 
sender immediately and permanently delete the original and any copy of this 
e-mail and any printout.
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to