https://github.com/bestpractical/rt-extension-notificationmatrix

https://github.com/bestpractical/rt-extension-notificationmatrix

Last synced: about 1 month ago
JSON representation

• Host: GitHub
• URL: https://github.com/bestpractical/rt-extension-notificationmatrix
• Owner: bestpractical
• Created: 2010-06-14T10:09:10.000Z (over 14 years ago)
• Default Branch: master
• Last Pushed: 2018-03-08T21:08:40.000Z (almost 7 years ago)
• Last Synced: 2023-04-13T18:31:29.342Z (over 1 year ago)
• Language: Perl
• Homepage: http://search.cpan.org/dist/rt-extension-notificationmatrix
• Size: 90.8 KB
• Stars: 3
• Watchers: 6
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README
  • Changelog: Changes

Awesome Lists containing this project

README

        
NAME

    RT::Extension::NotificationMatrix - RT Extension for custom ticket

    notification

PREREQUISITES

    This version of RT::Extension::NotificationMatrix requires at least RT

    4.2.x

    If you're running an older version of RT, you should seek an older

    version of this extension; specifically, version 2.2.

SYNOPSIS

      # In your RT site config:

      Set(@Plugins,(qw(RT::Extension::NotificationMatrix));

      # If you'd like to Bcc all recipients, uncomment the line below.

      # Disabled by default.

      #Set($NotificationMatrixAlwaysBcc, 1);

      # If you'd like to send on the Batch stage of transactions, uncomment the line below.

      # Default is "TransactionCreate"

      #Set($NotificationMatrixStage, "TransactionBatch");

DESCRIPTION

    This plugin provides per-queue configuration for notification triggering

    based on ticket actions, and notification delivery for selected ticket

    roles and/or user-defined groups.

    Note that this plugin can co-exist with the RT::Scrip-based

    notification, which you probably want to disable to avoid duplicated

    messages.

    When the plugin is enabled, you will have an additional Notification tab

    in the queue admin page. When a notification rule is triggered, the

    designated ticket roles or user defined groups get a message with the

    first found template of:

    $RuleName

        For example: TicketResolved

    The default tempalte defined by the rule

    The Transaction template

    Message sent to external recipients (requestors and ccs) will be using

    first found template of:

    $RuleName-External

        For example: TicketResolved-External

    The default external tempalte defined by the rule

    The Transaction template

CAVEATS

    Internally, the matrix is stored on the queue object as attributes, with

    mappings to the subscribe RT::Group object ids. The role groups are

    stored as queue-role groups, as at the time of configuration we do not

    have ticket instances to create ticket-role groups. The queue-role

    gorups are then instantiated as ticket-role when the notification rules

    are triggered.