Difference between revisions of "Transaction"

From Request Tracker Wiki
Jump to navigation Jump to search
Line 38: Line 38:
*OpenReminder
*OpenReminder
*ResolveReminder
*ResolveReminder
====Usage====
In scrips you can for example use it like this in custom contition:
<source lang="perl"><pre>
# On Create or Queue change
return 0 unless (($self->TransactionObj->Type eq "Create") || ($self->TransactionObj->Type eq "Set" && $self->TransactionObj->Field eq "Queue"));
</pre></source>

Revision as of 09:56, 7 February 2019

A Transaction in RT is anything that happens to a Ticket.

RT logs each transaction in the history of the ticket, and Scrips may also be attached to all or to certain kinds of transactions.

Common transactions are Comments and Correspondence

All types of transaction from lib/RT/Transaction.pm:

  • Create
  • Enabled
  • Disabled
  • Status
  • SystemError
  • AttachmentTruncate
  • AttachmentDrop
  • AttachmentError
  • Forward Transaction
  • Forward Ticket
  • CommentEmailRecord
  • EmailRecord – is set when sending notification (correspondence, comment) by rt-crontool
  • Correspond – is set when some user sends a correspondence
  • Comment – is set when some user sends a comment
  • CustomField
  • Untake
  • Take
  • Force (forced owner change)
  • Steal
  • Give
  • AddWatcher
  • DelWatcher
  • Subject
  • Addlink
  • DeleteLink
  • Told
  • Set (password, queue, date/time, owner)
  • Set-TimeWorked
  • PurgeTransaction
  • AddReminder
  • OpenReminder
  • ResolveReminder

Usage

In scrips you can for example use it like this in custom contition:

<pre>
# On Create or Queue change
return 0 unless (($self->TransactionObj->Type eq "Create") || ($self->TransactionObj->Type eq "Set" && $self->TransactionObj->Field eq "Queue"));
</pre>