Notification Providers

Mail Server

These are standard mail providers which send messages on a given email address about any changes regarding SLAs, or issues and projects.

Here we have two options:

1. Jira Mail Provider, or
2. Custom Mail Provider. 

By clicking the Add button on the right-hand side of the initial page, you start to create your Mail Notification Provider.

Please note that the Port field is the SMTP port. For the Jira Mail Provider, it is necessary to update the SMTP mail server.
In order to do so choose System > Mail > Outgointg Mail and then enter the requested infromation. 
If you are not sure how to configure Jira's SMTP server, refer to Atlassian documentation. The link is available at the bottom of this page. 

The image below shows the configuration of the Custom Mail Provider:

Slack Channel

In order to be a member of an existing Slack workspace, you will have to join one first. In this notification provider, everything happens on a workspace which is a group of people using Slack together. For this reason it is best to add our notification app to your Slack channels and workspaces. You can install it by clicking the Add to Slack button.

In this case the authorization is based on a Slack token. The required token should appear on your screen after the installation. 

When creating a Slack provider, you have to decide if you want the notification to be sent by a user or by a bot. If the Username field (Bot name) will be completed and the As a user field will be marked false, the message will be sent by a bot with the name you have previously entered. 

Hipchat Room

Hipchat is fully integrated with Jira services and acts similarly to Slack, the difference being that you have to start or join a group and specify to which room the message should be sent. What's important about thiis configuration, is to create your own integration with SLA Notifications in Hipchat. The authorization is based on your room ID and your token. This data can be accesed to when registering or checking Hipchat room details.

SMS / REST API Gateway

In this case there are four provider options available: 

1. Twilio,
2. SMS API,
3. CLX,
4. Custom text message.

 Twilio SMS

In order to configure your Twilio, you have to register on the Twilio website. Then check, in the console view, what is your Account SID and token. This information is necessary to create the selected notification provider.

SMS API

Whenever you create an SMS API provider, your Authorization field shows automatically the default authorization type. Since two authorization types are available, you can decide which of them is more suitable for you. These are:

• Basic authorization which is based on your SMS API Username and Password, and
• Token authorization which requires a unique token from the message provider. 

To begin the configuration process, you have to be registered in the SMS API portal which allows you to generate your token for authorization. 

Custom SMS

Custom SMS allows to configure the SMS provider of your choice. You will have to manually configure and make changes to your SMS provider settings such as, e.g. authorization type (token or basic), your provider's URL address and JSON data. 

Depending on your SMS service provider's requirements, you will have to select header content type, JSON requested data or Key/Value parameters. 

CLX SMS

If you wish to use CLX SMS as a notification provider, you have to set up your account on the CLX portal. Next go to the CLX Customer Portal and find your requested SID and token. 

Continue with your notification provider customizations, by adding and editing name and description.