...
For each provider the requirement parameters are different. Below is a table of the supported providers and the required parameters for successful configuration. More information on these parameters can be found in the respective providers documentation.
SMS Provider | Required Parameters | Documentation Reference |
---|---|---|
Twilio |
| |
BulkSMS |
| |
Nexmo |
| |
Clockwork |
| https://www.clockworksms.com/doc/easy-stuff/http-interface/send-sms/ |
Info |
---|
Each provider charge differently, please refer to their FAQ and pricing policies. |
Example (Twillio)
Once you have signed up, the necessary info for the Transport will be found on the post-login screen:
...
Configuring the SMS transport
...
Go to JEMH Cloud > Notifications > SMS > Create
Complete the form, select the nominated projects, select the SMS transport you want to use and the phone numbers (CSV) that will receive SMS message. Enter a velocity script if you want to modify the notification behaviour at runtime (more below).
On Submit, you should see the new SMS mapping
To test the mapping, create an issue in the nominated project and go to Auditing → Events
You should see the issue created event in the queue. When event has been processed, the configured phone numbers in the mapping should have received an SMS message.
The report of the event should confirm the message sent
In Auditing → Outbound Messages, the table should show the SMS messages sent and the cog icon should show their contents.
Send SMS Notifications from Post Functions
...
Change to phone number when Critical
|
Restrict notifications to specific time ranges
Notify only after hours
|
Restrict by priority
Code Block |
---|
#if ($context.issue.fields.priority.name.textValue() != 'Blocker') ## if issue priority is not a blocker $smsNotificationUtils.inhibitNotification() ## prevent current SMS notification #end |
...