Cristopher, I'm curious. Why not just have these tickets created in a "General" or "Review" Queue and send a notification to whoever should approve of the ticket based on "From" or some CF value. Then when that Approver changes the value of a CF to indicate approval, move the ticket to the appropriate Queue? That way, all history stays with the original request ticket.
Kenn LBNL On Tue, Jun 28, 2011 at 7:49 AM, Christopher Lasater <clasa...@taleo.com>wrote: > Ohh yeah, this is RT-4.0. Is this also the behavior in previous versions? > **** > > ** ** > > *From:* rt-users-boun...@lists.bestpractical.com [mailto: > rt-users-boun...@lists.bestpractical.com] *On Behalf Of *Christopher > Lasater > *Sent:* Monday, June 27, 2011 3:26 PM > *To:* rt-users@lists.bestpractical.com > *Subject:* [rt-users] Ticket can be Resolved when Depending on Rejected > Approval Ticket**** > > ** ** > > Hello,**** > > Not sure if this is normal, but I have a Queue set up so > that when a ticket is created it will automatically create another ticket > for Approval. This seems to be working well, since the original ticket is > immediately created with a Dependency for the Approval ticket. If I try to > Resolve the ticket before the approval process I get a dependency error, > which is what I expect, but if I reject the approval I can then resolve the > original ticket. Shouldn’t I get an error message at this point saying it > cannot be resolved and needs to be rejected? Or have the approval > automatically reject/close/resolve the original ticket?**** > > ** ** > > Thanks**** > > ** ** > > ** ** > > *Christopher Lasater > **Technology Analyst I > **Taleo > ** > **T. 904.520.6046 > E. clasa...@taleo.com > *[image: TALEO] <http://www.taleo.com/>**** > > *This email and any attachments thereto may contain private, confidential, > and privileged material for the sole use of the intended recipient named in > the original email to which this message was attached. Any review, copying, > or distribution of this email (or any attachments thereto) by others is > strictly prohibited. If you are not the intended recipient, please return > this email to the sender immediately and permanently delete the original and > any copies of this email and any attachments thereto.***** > > ** ** > > > -------- > 2011 Training: http://bestpractical.com/services/training.html >
-------- 2011 Training: http://bestpractical.com/services/training.html