[rt-users] Ticket can be Resolved when Depending on Rejected Approval Ticket

Kevin Falcone falcone at bestpractical.com
Wed Jun 29 16:29:30 EDT 2011


On Tue, Jun 28, 2011 at 10:49:20AM -0400, Christopher Lasater wrote:
>    Ohh yeah, this is RT-4.0.  Is this also the behavior in previous versions?

When you reject an Approvals ticket it should cascade that Reject back
up to the Original ticket automatically.  That is built-in default
behavior.

There is no code to prevent you from resolving it after it has been
rejected.

-kevin

>    From: rt-users-bounces at lists.bestpractical.com
>    [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Christopher Lasater
>    Sent: Monday, June 27, 2011 3:26 PM
>    To: rt-users at 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. [1]clasater at taleo.com
>    [2]TALEO
> 
>    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.
> 
> 
> 
> References
> 
>    Visible links
>    1. mailto:clasater at taleo.com
>    2. http://www.taleo.com/



> -----BEGIN PGP SIGNATURE-----
> Version: 10.1.0 (Build 860)
> 
> iQEVAwUBTgnp8HUEnna91A87AQiAfggApHjAjR18f+ngBCyoMQASu4ez5Ae/Xzgk
> PtCumIiFmqyAvQcXKFIysehccqQUdMUbz109Gq1JE9EMSxG2C/s9UOsCPGSE+VIL
> XKmC72S3ng2ii0URBXeyOKgxiE2hUMGgPYG6N0TIe45O+LQxe6GA7bibIHqrbekT
> mf2nkaJzuq7Mnq06NO4EJrGE9RnBq63BVIYwkWHY324OEKd+skhgOOADnhSs0+t7
> KSomVp2LUSrd/uwhexo+pYAb8Yy9bN2y3yMUW85Tqj2XfEeQ4CD4icafzSizwNCH
> /pQCZDk2rmQXIQc+liFlBgotfh+iFErXoP9sZ8l9s7mTjT021XkjCg==
> =ZVsj
> -----END PGP SIGNATURE-----


> 
> --------
> 2011 Training: http://bestpractical.com/services/training.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20110629/ecbcd2e8/attachment.sig>


More information about the rt-users mailing list