For the complex situation you described, I think the following scenario is the
best:
Release --> Change/Activity --> Task
Approvals can be configured for releases, so you won't be missing that initial
approval.
Also as you know, you can relate task templates to change templates, to
"standardi
Just my 2 cents here - yes "Copy to New" is "Broken in ITSM" - create a P1
ticket with BMC on the errors - per module...
The CNTL-T function is utilized A BUNCH for other reasons...
Robert
On Sat, Jul 24, 2010 at 4:29 AM, Kelly Deaver wrote:
> **
> Please DON'T add copy to new as an AR enhance
**
Clair,
Contact your BMC sales person and ask him for competitive intel on Axios. BMC generally has information on why they are better than any of their competitors ;)
Kelly DeaverL-3 Stratis / FAA Contractor
kdea...@kellydeaver.com (ARSlist mail)kelly.ctr.dea...@faa.gov (Business mail)
---
**
Please DON'T add copy to new as an AR enhancement. With the way hidden fields work in ITSM, it is an evil we fight daily. I end up with all kinds of bad results from people using copy to new on Incident and People records. The applications should have a standard copy to new function like the one
4 matches
Mail list logo