Raley can listen to the following events in your JIRA and react on them:
Listening and notifying based on the following Jira ServiceDesk-specific events:
Our AddOn supports JIRA issue status change notification allowing you to define one or multiple start and end status(-es). When transition from A to B is happening, Raley will notify users of your choice.
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. You can define your own custom condition based, for example, on data in Jira issue, who is commenting on the ticket or the new value in the custom field.
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. One of the most typical digests is notifying assignees about their tasks due in the past
Allows you to predefine a notification that will be available in issue detail view for specific project and issue type(s). It will be sent when a user in your Jira will pick up the appropriate notification from Raley glance and click Send button.
You can notify:
Raley can send notifications to ANY email address or Slack channel.
You can send notifications using TO, CC or BCC email options
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. To simplify the templating you can use our Template Wizard.
Raley transparently handles images added as inline attachments to JIRA or ServiceDesk comments, so that email recipients will see them embedded in email
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.
Notification recipients can be configured dynamically. This applies to email addresses. 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.