Bot::Backbone::Service::Ticket::Tracker - role implemented by ticket lookup whatsits


version 0.160490


    # To make a new ticket tracker lookup whatsit...
    package Bot::Backbone::Service::Ticket::Tracker::MyTicketSystem;
    use Moose;

    with qw( Bot::Backboen::Service::Ticket::Tracker );

    use WebService::MyTicketSystem;

    has uri        => ( is => 'ro', isa => 'Str', required => 1 );
    has auth_token => (is => 'ro', isa => 'Str', required => 1 );

    sub lookup_issue {
        my ($self, $number) = @_;

        my $tracker = WebService::MyTicketSystem->new(
            uri   => $self->uri,
            token => $self->auth_token,

        my $issue = $tracker->lookup($number);

        return {
            summary => $issue->title,
            issue   => $issue->id,
            details => $issue->description,


    # And then in your bot configuration:
    service my_tickets => (
        service  => 'Ticket',
        trackers => [{
            type       => 'MyTicketSystem',
            uri        => '',
            auth_token => 'gobbledygooksecretstuff',
            title      => 'Ticket #%{issue}s: %{summary}s',
            link       => '{issue}s',
            patterns   => [


This is the role implemented by a ticket tracking system to perform lookups.



Required. This is a String::Errf format pattern used to create the title of the issue to return to chat. it will be passed the hash returned by "lookup_issue" to fill.

Optional. This is a String::Errf format pattern used to create a link when needed. It will be passed the hash returned by "lookup_issue" to fill.

If not given, links will never be shown.


Required. This is an array of regular expressions that match issues in some text. Each one must use named pattern groups and must include at least an "issue" group. It may also contain a "scheme" group. The "issue" is the issue number and the "scheme" is used to identify whether or not the matched pattern contains a link. The actual content of "scheme" is ignored, but is usually "http:" or "https:".

Since every company and workgroup has its own nomenclature, the patterns are almost always context-specific, so there are generally no default patterns. There is nothing stopping some ticket tracker from implementing such default, though.



  my %info = %{ $service->lookup_issue($number) };

Given an issue identifier found using one of the "patterns", this should return a hash of information to be used with "title" and "link" to render that information back to the end-user.



  my @titles = $service->titles_for_string($string);

Given a string to evaluate, return all the titles of all the issues found in it.


  my $title = $service->issue_title($number, $show_url);

This method is passed the result of a matching pattern from "patterns". The first argument is "issue" match and the second is based on the presence of a "scheme" in the match. If a "scheme" is found then $show_url will be false (i.e., they already have the link, we don't need to send it again).

This method calls "lookup_issue" to get information about the issue and uses that to generate the title.

The result is built using the "title" and "link" attribute values.

  my $link = $service->issue_link(\%issue);

Returns the link text to use. Passed the issue hash returned by "lookup_issue".


Andrew Sterling Hanenkamp <>


This software is copyright (c) 2016 by Qubling Software LLC.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.