Notification Provider specifies the method of informing users about their SLAs. It may be defined as a communication channel.
These include configuring an already existing mail provider, creating a new custom SMS provider, and adding Slack or Hipchat as notification providers.
Info | ||
---|---|---|
| ||
Using Slack, Hipchat or working constantly with the mobile phone in your hand? This feature will always keep you informed about your SLAs. |
Adding a Provider:
- Log in as a user with the Jira Administrators global permission.
- Choose the cog icon> Add-ons. Select SLA PowerBox > Notification Providers to open the SLA Notification Providers page.
Tip: Keyboard shortcut: g + g + start typing notification providers... - Click the Add Provider button.
- Select you Provider type. There are four options available.
- Confirm your choice with the Next button.
- You will be redirected to the Create Notification Provider page. Follow the configuration steps specified for each Provider type.
Editing a Provider:
- Log in as a user with the Jira Administrators global permission.
- Choose the cog icon> Add-ons. Select SLA PowerBox > Notification Providers to open the SLA Notification Providers page.
Tip: Keyboard shortcut: g + g + start typing notification providers... - Select Edit in the Operations section
- Confirm with the Save button.
Info | ||
---|---|---|
| ||
When editing the Provider you can change it only within one Provider type, i.e. one SMS provider to another SMS provider. You cannot change Providers between different types. |
Deleting a Provider:
- Log in as a user with the Jira Administrators global permission.
- Choose the cog icon> Add-ons. Select SLA PowerBox > Notification Providers to open the SLA Notification Providers page.
Tip: Keyboard shortcut: g + g + start typing notification providers... - Select Delete in the Operations section.
- Confirm with the Delete button.
Disabling a Provider:
- Log in as a user with the Jira Administrators global permission.
- Choose the cog icon> Add-ons. Select SLA PowerBox > Notification Providers to open the SLA Notification Providers page.
Tip: Keyboard shortcut: g + g + start typing notification providers... - Select Disable in the Operations section.
- Confirm with the Disable button.
Enabling a Provider:
- Log in as a user with the Jira Administrators global permission.
- Choose the cog icon> Add-ons. Select SLA PowerBox > Notification Providers to open the SLA Notification Providers page.
Tip: Keyboard shortcut: g + g + start typing notification providers... - Select Enable in the Operations section.
- Confirm with the Enable button.
Note | ||
---|---|---|
| ||
By selecting the Test Notification option, you check if the notifications will be sent properly.Below you can find different configuration screens. They may vary depending on the previously chosen Provider. |
Sending a text notification using a Provider:
- Log in as a user with the Jira Administrators global permission.
- Choose the cog icon> Add-ons. Select SLA PowerBox > Notification Providers to open the SLA Notification Providers page.
Tip: Keyboard shortcut: g + g + start typing notification providers... - Select Send test notification in the Operations section.
- Configure your test Notification fields.
- Confirm with the Send button.
- .
Configuring a test notification:
- Log in as a user with the Jira Administrators global permission.
- Choose the cog icon> Add-ons. Select SLA PowerBox > Notification Providers to open the SLA Notification Providers page.
Tip: Keyboard shortcut: g + g + start typing notification providers... - Select Send test notification in the Operations section.
- Configure your test Notification fields.
- Confirm with the Send button.
- .
Sms test notification
Slack test notification
Mail test notification
Hipchat test notification
Useful links: www.twilio.com, www.support.twilio.com, www.slack.com/get-started/, www.clxcommunications.com, www.smsapi.pl, www.stride.com, https://confluence.atlassian.com/adminjiraserver075/configuring-jira-s-smtp-mail-server-to-send-notifications-935391635.html
...