<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello all!<br><br>I've run into a minor annoyance in the SelfService interface of our RT 3.6.6 install at work. If an unprivileged requestor attempts to resolve an open ticket, the ticket will be set to "Resolved" but then re-open immediately due to their correspondence being added to the ticket *after* the ticket is resolved.<br><br>(The rights assigned to the "Requestor" and "Unprivileged" groups in this queue are CreateTicket, ModifyTicket, ReplyToTicket, SeeQueue, and ShowTicket.)<br><br>Here's an example of this behaviour, with the earliest transaction listed first:<br><br>Tue Apr 29 11:50:28 2008 <span class="Apple-tab-span" style="white-space:pre"> </span> rt-testuser - Status changed from 'open' to 'resolved'<br>Tue Apr 29 11:50:28 2008 <span class="Apple-tab-span" style="white-space:pre"> </span> rt-testuser - Correspondence added<br>"resolution test... disregard..."<br>Tue Apr 29 11:50:28 2008 <span class="Apple-tab-span" style="white-space:pre"> </span> RT_System - Status changed from 'resolved' to 'open'<br><br>This differs from the behaviour of the full, privileged RT interface of the same install, in which correspondence from a SuperUser is added, THEN the status is changed. I don't seem to have any scrips in place that would cause this behaviour, and I've verified the same behaviour in a separate (more basic) RT 3.6.4 install.<br><br>I don't wish to prevent correspondence from re-opening tickets, as it's rather useful to us, but I WOULD like to fix this behaviour in SelfService :)<br><br>Does the hive mind have any ideas?<br><br>Thanks for your time!<br><br>-Matt<br></body></html>