Raley can listen to the following events in your JIRA and react on them:
- workflow status changed
- comment added
- comment added
- comment updated
Our AddOn supports JIRA issue status change notification allowing you to define define one or multiple start and end status(-es). When transition from A to B is happening, Raley will notify users of your choice.
Allows you to predefine a notification that will be available in issue detail view for specific project and issue type(s). Your Jira user would click on Raley Emails Notifications glance, pick up the right template and send the email.
Notify both internal and external users
- Issue watchers
- Mentioned users
- all users in Jira group
- all users in particular ServiceDesk
- all users in particular project's organizations
- project lead
- component lead
- service desk participants
- request approvers
- 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 ANY email address , or Slack channel or HipChat room.
You can send notifications using TO, CC or BCC email options
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. To simplify the templating you can use our Template EditorWizard.
Support for inline attachments
Raley notification can send JIRA issue attachments via email or slack message.Slack message.
Approve and Decline tickets via email
Add Approve and Decline buttons to your notification on Service Request with Approvals ticket. Approvals would be able to approve or decline the request simply by pressing a button in the email. More information about this feature you can find here
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, 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.