Notifying on JIRA events
Raley can listen to the following events in your JIRA and react on them:
- workflow status changed
- comment added
Notifying on Service Desk events
Listening and notifying based on the following ServiceDesk-specific events:
- Request commented internally
- Request commented publicly
Notify on workflow transition
Our AddOn supports JIRA issue status change notification allowing you to define start and end status. When transition from A to B is happening, Raley will notify users of your choice.
Full control on triggering notifications
Notifications are configured per project, issue type(s), and event. Digested messaging is using JQL conditions to cherry-pick the issues your team is interested in.
Produces aggregation of changes, comments and work-log entries per JIRA issue for given period of time. You can specify a time intervals like once per day, once per hour, once per week on specific days etc.
Allows you to predefine a notification that will be available in issue detail view for specific project and issue type(s).
Notify both internal and external users
Notifying reporter, assignee, issue watchers, project lead, component lead, service desk participants, approvers and organisations. You can send notification to any address which is backed by JIRA field of type "user". Besides that, you can specify JIRA field of "text" type to retrieve addresses from.
Raley can send notifications to any email address, Slack channel or HipChat room.
Fully customisable content and design of the message
AddOn users have complete freedom in defining content, layout and styling of the message. You can apply any HTML constructs to make your email truly custom and fitting your corporate style guidelines.
Support for inline attachments
Raley transparently handles images added as inline attachments to JIRA or ServiceDesk comments, so that email recipients will see them embedded in email
Send issue attachments
Raley notification can send JIRA issue attachments via email or slack message.
Raley Notification can store all copies of the notifications sent out for later audit in issue comments.
Dynamic resolution of recipients addresses
Notification recipients can be configured dynamically. This applies to email addresses, Slack channels and HipChat rooms. You can either choose JIRA fields that contain addresses or use Velocity template to implement your own conditional logic for defining who should receive the message based on the data in current issue.