Documentation Index
Fetch the complete documentation index at: https://docs.raleyapps.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
These tutorials walk you through setting up the most common notification types from scratch. Complete them in order if you’re new to Raley Emails Notifications.Lesson 1 — Your Very First Notification: On Status Change
Set up a notification that fires when a Jira issue moves to a specific workflow status. What you’ll build: An email that notifies the assignee when an issue transitions to “In Review.” Steps:- Go to Apps → Raley Emails Notifications in your Jira project
- Click Add new notification
- Name it:
Notify assignee on In Review transition - Set Event to: Issue Workflow Transition
- Set the Status (to) filter to:
In Review - In the Message Template, use a basic template or the Template Wizard to add the issue summary and a link
- Set Destination to:
Assignee - Click Save and test with Preview using a relevant issue key
Lesson 2 — Notifying a Customer When a Comment Is Added
Send an email to the customer whenever a public comment is added to their JSM service request. What you’ll build: A customer-facing notification triggered by a public JSM comment. Steps:- Create a new notification
- Name it:
Customer comment notification - Set Event to: Issue Commented
- Add a Condition: Comment visibility = Public (to exclude internal notes)
- Build a template that includes: the issue summary, the comment text, and a link to the portal request
- Set Destination to: Reporter (the customer who raised the request)
- Save and test
#if ($comment.visibility == "public") in your template if you want to conditionally include the comment only when it’s public.
Lesson 3 — Digest Notification
Send a daily summary email instead of individual notifications for every change. What you’ll build: A daily digest of all high-priority issues updated in the last 24 hours. Steps:- Create a new notification
- Name it:
Daily high-priority digest - Set Event to: Scheduled / Digest
- Set the Schedule to run daily (e.g., every day at 8:00 AM using a CRON expression:
0 8 * * *) - Set a JQL Filter to scope which issues are included:
priority = High AND updated >= -24h - Build the template using
#foreachto iterate over matching issues and display their key, summary, status, and assignee - Set Destination to the team email address or distribution list
- Save and test
Lesson 4 — Digest Notification with Fields and Comments Change Log
Build a more advanced digest that shows what changed on each issue, including field changes and new comments. What you’ll build: A weekly digest of sprint issues showing each issue’s activity summary — fields changed, comments added — since the last digest. Steps:- Create a new notification
- Name it:
Weekly sprint activity digest - Set Event to: Scheduled / Digest
- Set Schedule to weekly (e.g., every Monday at 9:00 AM)
- Set a JQL Filter targeting the current sprint:
sprint in openSprints() - In the template, use the change log variables to show:
- Issues where fields changed since the last run
- Comments added since the last run
- Current status, assignee, and priority
- Use
#foreachto loop through the issue list and#ifto only show issues that had activity - Set Destination to the team lead or project manager
- Save and test with a preview run
Next Steps
After completing these tutorials:- Templating — full reference for template variables and Velocity syntax
- Cookbook — solutions to 40+ specific notification scenarios
- Troubleshooting — if notifications aren’t arriving as expected
Need Help?
- Service Portal: inversionpoint.atlassian.net/servicedesk
- Email: support@raleyapps.com
Explore Other RaleyApps
Raley Intake Forms
Create powerful intake forms directly inside Jira and JSM.
Raley Procurement and Quotation
Manage purchase orders and sales quotes from within Jira.
Raley Bookman
Asset booking management inside the JSM portal.
Raley Favorites
Save and quickly access your most important Jira issues.