Date: Fri, 29 Mar 2024 05:12:24 -0400 (EDT) Message-ID: <1967675548.3779.1711703544935@wiki.jirassimo.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3778_466542710.1711703544927" ------=_Part_3778_466542710.1711703544927 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Raley can listen to the following events in your JIRA and react on them:=
Listening and notifying based on the following ServiceDesk-specific even= ts:
Our AddOn supports JIRA issue status change notification allowing y= ou to define start and end= status. When transition from A to B is happening, Raley will notify u= sers of your choice.
Notifications are configured per project(s), issue type(s), and event. D= igested messaging is using JQL conditions to cherry-pick the issues your te= am is interested in. You can define your own logic that will further enhanc= e whether the notification should be fired or not based on data in specific issue.
Produces aggregation of changes, comments and work-log entries per JIRA&= nbsp;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 d= etail view for specific project and issue type(s). User can customise a pre= -generated message before sending it out.
Notifying
You can send notification to any address which is backed by JIRA fi= eld of type "user" or "group". Besides that, you can specify JIRA field= of "text" type to retrieve addresses from.
Raley can send notifications to any email address (MIME and text/Plain),= Slack channel or HipChat room.
You can optionally notify send CC and/or BCC emails together with major = notification email. This feature is supported for Jira issue events, Servic= e desk events, Canned messaging, project and version events
AddOn users have complete freedom in defining content, layout and stylin= g of the message. Show any standard or custom Jira field as well as Element Connect fields. You can apply any HTML constructs= to make your email truly custom and fitting your corporate style guideline= s. Customise message depending on target user's preferred language!
Raley transparently handles images added as inline attachments to JIRA o= r ServiceDesk comments, so that email recipients will see them embedded in = email
Raley notification can send JIRA issue attachments via email or slack me= ssage.
Raley Notification can store all copies of the notifications sent out fo= r later audit. Complete log of messages is available under "Raley Audit" ta= b in issue detail view.
Notification recipients can be configured dynamically. This applies to e= mail addresses, Slack channels and HipChat rooms. You can either choos= e JIRA fields that contain addresses or use Velocity template to implement = your own conditional logic for defining who shoul= d receive the message based on the data in current issue.
Your notification can be sent either using standard outgoing email serve= r which is provided by Jira, or, alternatively, using your own custom SMTP = server account. The latter is useful for setting up JSM service desks Email= Requests where you want to notify customers using the same account from wh= ich service requests are created.
You don't have to write a single line of template to get your first noti= fication up and running. Raley will pre-generate the message template for y= ou automatically!
Both, JIRA admin and project admins can configure their own notification= s. While project admin is limited by his or her project(s), JIRA admin= istrator can configure notifications for any project.