Skip to main content

​
OnDemand hosting

​
Raley Emails Notifications

Our Notifications add-on is installed with READ, WRITE, ADMIN, and ACCESS_EMAIL_ADDRESSES permissions in the Atlassian Connect descriptor, which means that it can do the following with your JIRA :  READ: issues, projects, and versions from your JIRA. WRITE: Raley Notifications can add comments to your JIRA issues when “Audit enabled” is turned on for specific notifications. The content of the comment is a textual value of the notification that Raley sends out for this issue. ADMIN: reading data of JIRA user and retrieving emails of members of specific JIRA group(s). ACCESS_EMAIL_ADDRESSES: retrieve ALL email addresses for all accounts in your Jira If you’re using sending to Slack or HipChat, then Raley will store the credentials you provide from those messaging platforms, which are necessary to send the notifications. It does not read any data from Slack or HipChat. If you use Email-based notifications, then:
  • if using your own SMTP outgoing mail server that requires authentication, then we will store the necessary username and password to send emails from it.
  • If you rely on a Raley-provided outgoing SMTP server, then notifications will be sent via the Mandrill app on behalf of Raley Notifications (notifications@raleyapps.com)
We do not persistently store the details of your JIRA issues/projects/versions on our servers. All communication between your JIRA and Raley Notifications is secured by a combination of SSL and JWT. We regularly back up your notifications configuration and store them for at least 30 days.

​
Authentication with Gmail OAuth 2

Raley Email Notifications for Jira/JSM can send emails from your Gmail account in your name. For that, it requires that you grant us access scopes: The first scope, as the name implies, is needed to send an email message under your name. The second scope (https://www.googleapis.com/auth/gmail.metadata) is required to retrieve the metadata of the email we’ve just sent to get the value of the Message-ID header. We’re storing the value of Message-ID on our side to refer to other emails (using the References header) that were sent for the same Jira/JSM ticket. This allows for a beautiful threaded view of all emails sent by Raley for a specific Jira/JSM ticket. The app is sending emails directly and not from the Drafts folder. For sending, we need to know your Gmail name and your Gmail email, which you provide during configuration of the Gmail OAuth2 outgoing email server in Raley. You connect your Gmail account with JSM to pick up new emails and create support tickets from them - this is JSM standard functionality (Email Requests). Raley allows you to connect the same Gmail mailbox for sending outgoing emails. As a result, all your ticketing is happening via a single Gmail account and thus greatly enhances the user experience for your JSM users (customers). We store the user’s name and email address as you provide those during Gmail OAuth2 configuration in Raley. These values are used to send emails from the given Gmail account. Raley Email Notifications for Jira/JSM’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

​
Raley IntakeForms

Our IntakeForms add-on is installed with READ, WRITE, and ADMIN permissions in the atlassian-connect descriptor, which means that it can do the following with your JIRA: READ: issue and project metadata from your JIRA necessary to create issues. WRITE: create issues (potentially, with attachments) in JIRA based on the form configuration that you set up.  ADMIN: create customers in your JIRA ServiceDesk, obtain information about your JIRA project metadata We do not store the data submitted via Raley IntakeForms and do not read issues from your JIRA. All communication between your JIRA and Raley IntakeForms is secured by a combination of SSL and JWT. The form is rendered in IFrame and  src is HTTPS-protected. We regularly back up your notifications configuration and store them for at least 30 days.

​
Raley Purchase Orders

Our PurchaseOrders app requires the following permissions through the Atlassian Connect descriptor: READ: issue-related information to create and manage purchasing workflow WRITE: to transition issues in the workflow ADMIN:  read project and workflow-related information to manage PO statuses, and information about your Jira users to handle your organization structure and users’ rights ACCESS_EMAIL_ADDRESSES: to send email notifications to Jira users when their approval of a Purchase Order is needed Raley PurchaseOrders stores information about your workflow statuses, existing project keys, and issue keys. Other issue-related data is not stored. We also store all the quantitative information about purchase orders, like lines, amounts, and summaries.  We do not store private user information. All the data stored in Raley PO is regularly backed up and stored for at least 30 days.  

​
Raley Bookman

The Bookman app requires the following permissions through the atlassian-connect descriptor: READ: issue-related information from the issues that match JQLs provided on the Bookman configuration page WRITE: assigning issue properties for Booking type of JSM requests DELETE: customer users can delete Booking type of JSM requests that were submitted by them Bookman does not store private user information. All the data stored in Raley Bookman is regularly backed up and stored for at least 30 days.  

​
Data storage and access

Raley cloud apps are hosted on digitalcloud.com and Amazon AWS servers. Physically, data centers are located in Amsterdam and the USA. Access to the Raley servers and data
is strictly limited to the RaleyApps support team. Our support team periodically inspects servers and data stored to troubleshoot issues and monitor application
performance.   

​
Data privacy

Data collected during the use of Raley AddOn will not be shared with third parties except as required by law.
When you uninstall this AddOn, we retain all of the data you’ve provided to us for a period of up to 60 days. After that period, the data is deleted.
   

​
RaleyApps with Server hosting

​
Notifications

Our Raley Notifications add-on for JIRA / ServiceDesk is an application that resides on your host JIRA server. It has access to the following data: READ:
  • single issue (and attachments) by key/id and multiple issues by JQL. For the latter, Raley uses the “jirassimo” user to perform a query; thus, you can finely tune data access by configuring access permissions for the “jirassimo” user.
  • Projects
  • Users
WRITE
  • Notification configurations and the actual emails sent by AddOn if auditing is enabled on a specific configuration

​
Data storage and access

Raley Notifications keeps all of its configuration in the host JIRA server and does not interact with other systems (except Email/Slack/HipChat as configured). No data is sent to any third party by this add-on. RaleyApps team does not collect any data from installations of Raley Notifications. 

​
Data backup

Raley Notifications does not provide any built-in facility for data backup. Instead, it relies on a backup of the host JIRA database to restore its function in case of disaster.  
Effective as of November 4, 2022.

​
Questions?

Can’t find what you’re looking for? Please contact us at Support
Last updated: August 19, 2026