On 01/29/2015 11:52 PM, Kevin Falcone wrote:
> On Thu, Jan 29, 2015 at 03:04:55PM -0500, Alex Vandiver wrote:
>> On Wed, 28 Jan 2015 14:27:22 +0100 Jasper Olbrich
>> wrote:
>>> Is it possible to suppress the status change from open to resolved
>>> with a scrip or to include the scrip-induced sta
On Jan 29, 2015, at 3:05 PM, Landon Stewart wrote:
> In the action (commit) section of the Scrip:
> $self->TicketObj->Status("open");
> $self->TicketObj->Comment( Content => "Script re-opened because
> CustomFieldName is
> ".$self->TicketObj->FirstCustomFieldValue("CustomFieldName") );
Oops. S
On Jan 28, 2015, at 5:27 AM, Jasper Olbrich
wrote:
>
> Hello,
>
> I want to cancel or undo the "Mark as Resolved" transaction based on the
> content of custom fields. Currently I'm using a Scrip and I'm only able to do
> the following:
>
> * access the custom fields
> * make the decision
> *
On Thu, Jan 29, 2015 at 03:04:55PM -0500, Alex Vandiver wrote:
> On Wed, 28 Jan 2015 14:27:22 +0100 Jasper Olbrich
> wrote:
> > Is it possible to suppress the status change from open to resolved
> > with a scrip or to include the scrip-induced status change in the
> > result box?
>
> Unfortunatel
On Wed, 28 Jan 2015 14:27:22 +0100 Jasper Olbrich
wrote:
> Is it possible to suppress the status change from open to resolved
> with a scrip or to include the scrip-induced status change in the
> result box?
Unfortunately, neither of these is possible in stock RT. Scrips can
only run _after_ a c
Hello,
I want to cancel or undo the "Mark as Resolved" transaction based on the
content of custom fields. Currently I'm using a Scrip and I'm only able
to do the following:
* access the custom fields
* make the decision
* comment on the ticket with the reason why it can't be resolved
* reopen
