I submitted this issue to BMC and they acknowledged this as remedy bug and recorded this as bug with ID SW00296610. Hopefully, it should be resolved in netxt patch.
On 5/23/08, Orndorff, Greg <[EMAIL PROTECTED]> wrote: > > My guess is that BMC is saying it's "by design" because for us, our > orphaned tasks remain open. So they must have at least fixed them in a > later patch so that they are Closed. > > We're currently on - > AR Server version and patch: 7.0.01 patch 005 > AR User version and patch: 7.0.01 patch 002 > Change Mgmt: 7.0.01 patch 003 > > > > Pegasus Solutions | BreakThrough > > Greg Orndorff > Applications Consultant > Enterprise Delivery > Phone: 480.624.6218 > To quickly log a ticket - click HERE! > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of T. Dee > Sent: Thursday, May 22, 2008 11:04 AM > To: [email protected] > Subject: Re: Chnage Management email notification issue > > We had a similar issue, that being when you create a Change and you > add Task(s), however, at the last minute you decided NOT to save the > Change record ALL the Task(s) associcated with the Change are set to > Status = Closed / Status Reason = Canceled. This results in Orphan > Records. > > According to Remedy this is by design. I'm not exactly sure why > Orphan records would be by design, but that is what I am told. > > If you click on the "Open" button to open the Change from the Orphan > Task it says something like "Requester is not available" - this is not > clear. > > The Change record does not exist, but all your Task(s) do. > > As well take note if you delete your Change record it does not warn > you about the Task(s), the result will be your Change record will be > delete, but your Task(s) will still exist - orphan records. > > > > > On 5/22/08, Wirasat Siddiqi <[EMAIL PROTECTED]> wrote: > > ** > > > > We are noticing that if someone fill out change request form using > select > > template options but for some reason changes his mind and does not > submit > > the change. In that case, tasks are getting generated and get closed > out. > > However, it is sending out email notification to some of the groups > that > > have assigned tasks. It should not send email notification when change > > ticket was not even submitted. > > > > Here are the environments we are using: > > > > OS: Linux SUSE 10 > > > > Database: Oracle 10g > > > > AR Server: 7.1 Patch 1 > > > > ITSM: 7.0.03 Patch 7 > > > > > > > > Thanks,Wirasat __Platinum Sponsor: www.rmsportal.com ARSlist: "Where > the > > Answers Are" html___ > > ________________________________________________________________________ > _______ > 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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
