Changes between Version 3 and Version 4 of HipChatRelayIntegration


Ignore:
Timestamp:
Jul 20, 2015, 5:16:31 PM (9 years ago)
Author:
figaro
Comment:

Removed nosource tag, tagged with license

Legend:

Unmodified
Added
Removed
Modified

  • HipChatRelayIntegration

    v3 v4  
    2929== Example
    3030
    31 The way it currently works is first a custom-field with pipe-separated values is chosen. In the admin panel, you then set chatroom names for each value found in the custom-field. There is a "default channel" option which will be used if the input is left blank. In the admin panel you also enter your API key from hipchat, and the "username" of the announce, like TracBot.
     31The way it currently works is to first select a custom-field with pipe-separated values. In the admin panel, you then set chatroom names for each value found in the custom-field. There is a "default channel" option which will be used if the input is left blank. In the admin panel you also enter your API key from hipchat, and the "username" of the announce, like TracBot.
    3232
    3333If you do not currently tag your tickets with a custom-field (like projectname), and you just want all tickets to be sent to one chat channel, just fill in the "default channel" option and that will happen.