v2.1

New

• PagerDuty integration - Receive PagerDuty alerts for Slab notifications.
  Currently, a plugins.toml file is required alongside the config.toml in the directory that Slab runs in.
  Also, an Events V1 integration is required on the PagerDuty side: https://support.pagerduty.com/docs/services-and-integrations#section-create-a-generic-events-api-integration
  When an alert is sent, PagerDuty will trigger an event to the service that has that integration key.
  Future versions of this plugin will allow for configuration at the tag level, as well as support for multiple integration keys.
  The plugins.toml should have this structure:

[PagerDuty]
 ServiceID="<-INTEGRATION KEY HERE->"

Fixed

• "Triage" function no longer drops tickets
  All tickets are now captured and pagination support for large ticket volumes is now properly supported.
• Log Level
  The log level flag used at the command line during startup now properly changes the log level. Supported level types are:
  • info
  • debug
  • error

v2.01

Hotfix Release:

Fix for date pull

v2.0

Slab v2.0!

Features:

Tag based notifications

• Report on any tag on a ticket - instead of a hardcoded list of 4 SLA types, any tag can be set up to receive alerts on new tickets, upcoming SLA breaches, or ticket updates, sent to any channel. See Configuring Tags for more details

Reporting

• Using Postgres, Slab now collects information about each time a command is run and saves it in the Activity table within the Postgres database.
• Future versions of Slab will create reports on who uses Slab the most, how long the average person uses Slab for, etc.

Display organization on SLA alerts

• Thanks to @li3n3, Slab now displays the organization associated with the given ticket on SLA alerts.

Fixes:

• Proper DB connection handling
• Use the new Slack standard for @here
• Redirect the @slab help message to the wiki, rather than a hardcoded list

v1.5

Changelog

• [FEATURE] - Persistent Data - Using a redis instance, Slab can now save the current Triager through restarts. Using a -db= flag on start up allows you to set a specific redis database.

• [FEATURE] - Premium Alerts - Based off of the tags set for SLA levels, new tickets with the higher priority tags can receive alerts when the tickets are received. This configurable behavior allows the team to be alerted whenever a new "premium" ticket is received.

• [BUGFIX] - Slab will properly handle paginated API calls, allowing for greater traffic of processing tickets.

Many minor improvements were made on the backend to help improve the stability of Slab, and allow for future expansion and development.

v1.4

Changelog

• [FEATURE] - Config Wizard - Configure Slab directly from Slack through an interactive configuration wizard! Currently, the channel Slab reports in and the Zendesk configuration details are the configurable options. This generates a config.toml located in the same folder that Slab is run from, which can then be customized further.
  

• [BUGFIX] - Slab no longer attempts to parse inaccessible Zendesk data

v1.3

Changelog

• [FEATURE] - Plugins - Third party plugins that integrate with Slab and provide additional notification functionality, such as Twilio. More information
• [BUGFIX] - Slab no longer crashes when the Zendesk API is unreachable
• [CHANGE] - Added timestamp to acknowledge message for further clarity

v1.2

Changelog

• [FEATURE] - More Info - When a ticket sends an SLA notification to Slack, you can now see more information about the ticket and who requested it with the new More Info button

• [FEATURE] - Colored notifications - based off of how long the ticket has left before the SLA timer expires.

• [CHANGE] - Updated logging to utilize sirupsen/logrus

v1.1

Changelog

• [FEATURE] - Triager role - enable the notification of new tickets through direct message, and stay on top of tickets as they come in to Zendesk
• [FEATURE] - Added Slack commands @slab set, @slab unset, @slab whois, @slab help @slab status.

  • @slab set
    Set returns a drop down menu of all available Slack members, allowing you to select a person to take the triager role. Note that this is all employees, and not just support. For the most part, this command will be used when setting yourself as triager.

  • @slab unset
    Unset returns Slab to its default state of having no triager. This means that the new ticket notifications will not be sent until a new triager is set.

  • @slab whois
    Whois returns the name of the person currently set as triager. If there is not currently a triager, or if unset was recently ran, this value will be None.

  • @slab help
    Help returns a list of all available Slab commands.

  • @slab status
    Status returns the server's metadata, including what version of Slab is running and what the uptime is.

• [BUGFIX] - Updated fork of Slack dependency to avoid rate limiting issues

v1.0

Changelog
[FEATURE] - Configurable port settings
[FEATURE] - Acknowledge button added for SLA breach messages
[BUGFIX] - SLAB crashes when EOF reached in Zendesk API