Yeah, I discovered that too when you change groups. I basically just went into the workflow to correct it. The fix included an update to the active link TMS:SHR:Change_AssigneeGroup_1. In that active link you have to add to the Set Fields action to set 'Assigned To ID' to NULL.
Although I didn't realize that it also doesn't cover when you blank out the Assigned Individual. Thanks Peter Lammey ESPN MIT Technical Services & Applications Management 860-766-4761 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of T. Dee Sent: Thursday, March 06, 2008 1:12 PM To: [email protected] Subject: OT: Defect - Task - SW00279798 - ITSM 7 (patch 6) Just an FYI - there is a defect in ITSM 7 - Task. If the Task is Assigned to someone (Bob Smith) and you "blank" out the person's name (Bob Smith) in the "Assignee" field and hit save it does not blank out the "Assigned To" field and this is the field that the Overview Console uses to list the Tasks assigned to you. I'm just going to create workflow on submit / modify that says if Assignee = $NULL$ then $NULL$ out Assigned To. Ty ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
