# Get started with RaleyApps
Source: https://docs.raleyapps.com/apps/Get-started-with-RaleyApps
Install any RaleyApps app for Jira or Jira Service Management from the Atlassian Marketplace, start a free trial, and reach your first result in minutes.
Every RaleyApps app installs the same way and follows the same trial model. This page walks you through the steps once, then points you to the first task for your app.
## Before you start
You need:
* A **Jira Cloud** or **Jira Service Management Cloud** site. Raley Bookman requires JSM.
* **Site admin** permissions on that site. Only admins can install Marketplace apps.
That is all. No servers, no separate accounts: every Raley app runs inside your Atlassian site.
## Not sure which app you need?
This page assumes you know your app. If you are still deciding, read [Which app solves which problem](/choosing-an-app) first: it matches your situation to the right app in 30 seconds and explains what each app is not.
## Install your app
Follow the [installation guide](/installation): it covers both install paths (inside Jira, or from the Marketplace website), verification, common problems, and uninstalling. The steps are identical for all 5 apps and take about 3 minutes.
## Trials, licensing, and billing
* Every app starts with a **free trial** from its Marketplace listing. Atlassian manages the trial period and all billing: you never give payment details to RaleyApps.
* Pricing scales with your Jira user tier. Current prices are on each app's Marketplace listing, which is always the authoritative source.
* Uninstalling from **Settings, Apps, Manage apps** stops billing. Check the [data security and privacy statement](/policies/data-security-and-privacy) for what happens to your data after you uninstall.
## Your first result, per app
Installed? Go straight to the first task:
| App | First task |
| ------------------- | --------------------------------------------------------------------------------- |
| Email Notifications | [Set up your first notification rule](/apps/emails-notifications/getting-started) |
| Intake Forms | [Build and publish your first form](/apps/intake-forms/getting-started) |
| Procurement | [Create your first purchase order](/apps/procurement/purchase-orders) |
| Bookman | [Configure asset sources and booking rules](/apps/bookman/configuration) |
| Favourites | [Pin your first issue](/apps/raley-favorites) |
## Get help
Stuck during setup? See [Support contact](/support) for how to reach us and what to include.
***
*Last updated: August 19, 2026*
# Install any Raley app from the Atlassian Marketplace
Source: https://docs.raleyapps.com/apps/Installation
Step-by-step guide to installing RaleyApps apps on Jira Cloud or JSM Cloud: from inside Jira or from the Marketplace website, plus verification and uninstall.
Use this guide to install any of the 5 Raley apps on your Jira Cloud or Jira Service Management (JSM) Cloud site. The steps are identical for every app. Time: about 3 minutes.
Not sure which app you need? Read [Which app solves which problem](/choosing-an-app) first.
## Prerequisites
* A **Jira Cloud** or **JSM Cloud** site. Raley Bookman - Asset Reservation for JSM requires a JSM site.
* You are a **Jira admin** on that site. Only admins can install Marketplace apps.
## Option 1: install from inside Jira
1. In Jira's top navigation, select **Apps**, then **Explore more apps**.
2. Search for **Raley** and open your app in the results.
3. Select **Free trial**. Atlassian installs the app on your site, usually in under a minute.
## Option 2: install from the Marketplace website
1. Open [our vendor page on the Atlassian Marketplace](https://marketplace.atlassian.com/vendors/1212475/raleyapps-inversion-point?ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=installation\&utm_content=vendor-page) and select your app.
2. Select **Try it free**, then choose the Jira site to install it on. You must be an admin of that site.
Both options end in the same place: the app installed on your site with a free trial running. For how trials convert to subscriptions and how billing works, see [Licensing and trials](/licensing-and-trials).
## Verify the installation
Open the **Apps** menu in Jira's top navigation. Your Raley app appears in the list. Select it once to confirm it loads.
Done. Pick your first task from the [per-app list](/Get-started-with-RaleyApps#your-first-result-per-app).
## If something goes wrong
| Symptom | Cause | Fix |
| ------------------------------------------------------ | ---------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| The install button is greyed out or missing | You are not a Jira admin on this site | Ask a site admin to install the app, or to grant you admin permissions |
| The app does not appear in the Apps menu after install | The page has stale state, or the install has not finished | Refresh the browser; then check **Apps**, then **Manage apps**, where installed apps are listed |
| You want Bookman but cannot find where it runs | Bookman works through the JSM portal, and needs a JSM site | Confirm your site includes Jira Service Management, then see the [Bookman configuration guide](/apps/bookman/configuration) |
Still stuck? [Contact support](/support).
## Uninstall an app
1. In Jira, select **Apps**, then **Manage apps**.
2. Select the app, then **Unsubscribe** or **Uninstall**.
Billing stops with your subscription. For what happens to your data afterwards, see the [data security and privacy statement](/policies/data-security-and-privacy).
***
*Last updated: August 19, 2026*
# Which RaleyApps app solves which problem
Source: https://docs.raleyapps.com/apps/choosing-an-app
A decision guide to the 5 RaleyApps apps for Jira and JSM: match your situation to the right app for notifications, intake forms, procurement, asset booking, or bookmarks.
All 5 RaleyApps apps live inside Jira and Jira Service Management (JSM), but each one solves a different problem. This page helps you pick. It explains the reasoning; when you are ready to install, go to [Get started](/Get-started-with-RaleyApps).
One question sorts most cases: **who needs to act, and on what?** Someone outside Jira submitting a request points to Intake Forms. Your team hearing about issue changes points to Email Notifications. A purchase that needs approval points to Procurement. A shared thing that gets double-booked points to Bookman. Your own daily issues point to Favourites.
## The 30-second answer
| Your situation | Your app | Get it |
| -------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "People miss updates because Jira's notifications are rigid and noisy" | [Raley Email Notifications for Jira & JSM](/apps/raley-emails-notifications) | [Marketplace](https://marketplace.atlassian.com/apps/1214045/raley-email-notifications-for-jira-jsm?hosting=cloud\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=choosing-an-app\&utm_content=email-notifications) |
| "Customers or colleagues without Jira accounts need to submit requests" | [Raley Intake Forms for Jira & JSM](/apps/raley-intake-forms) | [Marketplace](https://marketplace.atlassian.com/apps/1217327/raley-intake-forms-for-jira-jsm?hosting=cloud\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=choosing-an-app\&utm_content=intake-forms) |
| "Purchasing runs on email and spreadsheets, and finance has no visibility" | [Raley Procurement - Intake & Approval Orchestration for JSM](/apps/raley-procurement-jira-jsm) | [Marketplace](https://marketplace.atlassian.com/apps/1223409/raley-procurement-intake-approval-orchestration-for-jsm?hosting=cloud\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=choosing-an-app\&utm_content=procurement) |
| "Meeting rooms, vehicles, or equipment keep getting double-booked" | [Raley Bookman - Asset Reservation for JSM](/apps/raley-bookman) | [Marketplace](https://marketplace.atlassian.com/apps/1237483/raley-bookman-assets-reservation-for-jsm?hosting=cloud\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=choosing-an-app\&utm_content=bookman) |
| "I keep re-searching the same handful of issues every day" | [Raley Favourites for Jira](/apps/raley-favorites) | [Marketplace](https://marketplace.atlassian.com/apps/1220204/raley-favourites-for-jira?hosting=cloud\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=choosing-an-app\&utm_content=favourites) |
Still deciding after the sections below? [Contact support](/support) and describe your workflow. We will tell you plainly which app fits, or whether none does.
## Raley Email Notifications for Jira & JSM
**Choose it when:**
* You want full control over who gets notified, when, and with what wording, based on issue events and conditions.
* You need emails or Slack messages to reach people Jira's built-in notifications cannot target, with your own templates.
* You want scheduled digest emails that summarize many issues in one message.
**Not the right fit when:** you need to collect information from people, rather than send it. That is Intake Forms.
Coming from Jira's built-in notifications? Read the [side-by-side comparison](/apps/emails-notifications/vs-jira-notifications).
## Raley Intake Forms for Jira & JSM
**Choose it when:**
* People without Jira accounts, such as customers, suppliers, or other departments, need to raise requests that become Jira issues.
* You want a branded form on your website or intranet, with validation, instead of email back-and-forth.
**Not the right fit when:** the submitters already work in Jira every day. Give them a request type or a workflow instead, and use Intake Forms for everyone else.
Weighing it against Jira's own options? See [Intake Forms vs Jira Cloud Forms and Issue Collector](/apps/intake-forms/vs-jira-cloud-forms) and [5 advantages over the Issue Collector](/apps/intake-forms/advantages-over-issue-collector).
## Raley Procurement - Intake & Approval Orchestration for JSM
**Choose it when:**
* Purchase requests need a real flow: intake, approval routing, a generated purchase order PDF, and delivery tracking, all inside the Jira or JSM ticket.
* You manage suppliers and product catalogs and want orders built from them, not typed from scratch.
* You also send customer-facing sales quotes and want them raised from the same place your team already works.
**Not the right fit when:** you only need a yes/no approval on an issue with no purchasing artifacts behind it. A Jira workflow with an approval step covers that without an app.
## Raley Bookman - Asset Reservation for JSM
**Choose it when:**
* Shared assets such as rooms, vehicles, or equipment need reservations with conflict detection, booked by customers or employees through the JSM portal.
* Your agents need to see an asset's current and upcoming reservations from the Jira work item screen.
**Not the right fit when:** you are scheduling people rather than assets, or you do not use JSM. Bookman requires a Jira Service Management site, and it books things, not meetings between colleagues.
## Raley Favourites for Jira
**Choose it when:**
* You, personally, keep navigating back to the same issues and want them pinned in one list, one click away.
**Not the right fit when:** you want a shared team view. Favourites lists are personal; for team-level views, use a Jira dashboard or board.
## Do the apps work together?
Yes. Each app is independent, so install only what you need, but they coexist on one site without conflicts, and they all operate on the same Jira issues. A request submitted through Intake Forms becomes a normal Jira issue, which means a notification rule in Email Notifications can react to it like any other issue. There is no bundle to buy and no shared configuration to maintain.
## Where to go next
* Ready to install: [Get started](/Get-started-with-RaleyApps) walks through the identical install flow for all 5 apps.
* Want depth on one app first: each app name above links to its overview, which explains what the app does and what it is not.
***
*Last updated: August 19, 2026*
# How RaleyApps runs on Atlassian
Source: https://docs.raleyapps.com/apps/how-raley-apps-run-on-atlassian
What Atlassian Connect and Atlassian Forge are, how they differ, and what each platform means for where your Jira data is processed.
Every Raley app runs on one of Atlassian's 2 app platforms: Connect or Forge. The platform decides where the app's code runs, who maintains that infrastructure, and where your Jira data is processed. This page explains the difference so you can answer a security review's first question before it is asked.
This is background reading. To install an app, see [Installation](/installation). For hosting, encryption, and GDPR details, see [Data security and privacy](/policies/data-security-and-privacy).
## Two platforms, one Marketplace
Apps on both platforms ship through the same Atlassian Marketplace and install the same way. The difference is architectural.
| | Atlassian Connect | Atlassian Forge |
| -------------------------------- | --------------------------------------------------- | -------------------------------------------------------------------------- |
| Where the code runs | On the vendor's own infrastructure | On Atlassian's infrastructure |
| Who runs and patches the servers | The app vendor | Atlassian |
| How it talks to your site | Signed REST calls over an encrypted connection | Inside Atlassian's cloud, behind platform controls |
| What that means for data | Data the app processes reaches the vendor's servers | Data stays in Atlassian's cloud unless the app is permitted to send it out |
### Connect: the app is a web service
A Connect app is a standalone web application. The vendor hosts and runs it, and it exchanges data with your site through Atlassian's REST APIs. At install time, your site and the app exchange a shared secret. Every call between the two is then signed with a JSON Web Token (JWT) built from that secret and sent over an encrypted HTTPS connection, so each side can verify who is calling and that nothing changed in transit. Atlassian documents this model in [Security for Connect apps](https://developer.atlassian.com/cloud/jira/platform/security-for-connect-apps/).
The trade-off: the vendor gets freedom to build on any language and stack, and in exchange the vendor, not Atlassian, owns the hosting and its security posture.
### Forge: the app runs inside Atlassian
A [Forge](https://developer.atlassian.com/platform/forge/) app is hosted entirely on Atlassian's infrastructure. Its code runs as functions inside Atlassian's cloud, in a sandbox that enforces tenant isolation and restricts data egress by design. The vendor still writes and maintains the app; Atlassian runs it.
The trade-off runs the other way: less infrastructure freedom for the vendor, stronger platform guarantees for you.
### Where the platforms are heading
Atlassian has spent years unifying the two platforms, moving Connect capabilities onto Forge step by step. Connect apps keep their Marketplace listings and customer installs through that transition. For the current state of the migration, Atlassian's [cloud app hosting guide](https://developer.atlassian.com/developer-guide/cloud-app-hosting/) is the source of truth.
## Which platform each Raley app uses
We list an app here once its platform is confirmed:
| App | Platform |
| ----------------------------------------------------------- | ----------------- |
| Raley Procurement - Intake & Approval Orchestration for JSM | Atlassian Forge |
| Raley Email Notifications for Jira & JSM | Atlassian Connect |
For any app, including the ones not listed yet, the authoritative record is the **Privacy & Security** tab of its Atlassian Marketplace listing. We add rows here as platforms are confirmed rather than guessing.
## What this page does not answer
* What data each app stores, where, and for how long: see [Data security and privacy](/policies/data-security-and-privacy).
* How to install or trial an app: see [Installation](/installation) and [Licensing and trials](/licensing-and-trials).
* What the Jira and JSM building blocks themselves are: see [Jira and JSM primitives RaleyApps build on](/concepts/jira-jsm-primitives-we-use).
Anything else, ask us through [Support](/support).
***
*Last updated: August 19, 2026*
# Introduction
Source: https://docs.raleyapps.com/apps/introduction
Install, configure, and get the most out of RaleyApps add-ons for Jira and Jira Service Management: notifications, intake forms, procurement, asset booking, and favorites.
RaleyApps builds 5 apps for Jira and Jira Service Management (JSM), available on the Atlassian Marketplace. Use these docs to install an app, configure it, and fix problems on your own. Every app follows the same structure: an overview, a getting started guide, task guides, reference pages, and troubleshooting.
## Find the right app
Each app solves one problem. Pick yours.
Jira's built-in notifications are too rigid. Send templated email and Slack messages on any issue event, with full control over recipients, conditions, and wording.
People outside Jira need to raise issues. Publish branded web forms that create Jira issues on submit. No Jira account required.
Purchasing runs on email and spreadsheets. Move purchase requests, approvals, purchase orders, and sales quotes into Jira, where your workflow already lives.
Rooms, vehicles, and equipment get double-booked. Let customers reserve assets through the JSM portal, with conflict detection built in.
You keep searching for the same issues. Pin the ones you work on most and open them in one click.
## Start here
The fastest first result for each app:
| You want to | Start with |
| ----------------------------------------- | --------------------------------------------------------------------------------- |
| Send your first custom email notification | [Set up your first notification rule](/apps/emails-notifications/getting-started) |
| Publish a form external users can submit | [Build your first IntakeForms form](/apps/intake-forms/getting-started) |
| Create your first purchase order in Jira | [Create and manage purchase orders](/apps/procurement/purchase-orders) |
| Take your first asset booking in JSM | [Configure asset sources and booking rules](/apps/bookman/configuration) |
| Bookmark the issues you use every day | [Raley Favourites overview](/apps/raley-favorites) |
Already set up? Jump straight to the guides in your app's sidebar section, or use search at the top of the page.
## Security and data
* [Data security and privacy](/policies/data-security-and-privacy): how each app accesses, stores, encrypts, and deletes your data, including GDPR details.
* [Service level agreement](/policies/service-level-agreement): our support commitments and response times.
* Security release notes live in each app's **Security releases** section in the sidebar.
## Get help
If a troubleshooting page does not solve your problem, see [Support contact](/support) for how to reach us and what to include.
![Atlassian Partner Designation Badge Silver Marketplace Partner Brand Background RGB @2x]()
***
*Last updated: August 19, 2026*
# Jira and JSM primitives RaleyApps build on
Source: https://docs.raleyapps.com/apps/jira-jsm-primitives
The Jira and Jira Service Management building blocks every Raley app works with, what each one is, and where you will meet it in these docs.
RaleyApps do not build a parallel system inside your site. They build on the same primitives your Jira admins already manage: work items, projects, request types, custom fields, and the query languages JQL and AQL. Know these 5 building blocks and every other page in these docs reads faster.
This is background reading, not a Jira admin course. Each section links to Atlassian's own documentation, which is the source of truth for how Jira itself behaves.
## Work items, which you may know as issues
A work item is the unit of tracked work in Jira: a task, a bug, a request, a reservation. Atlassian has renamed issues to work items across its cloud products, and older screens, APIs, and JQL keep the word issue for backward compatibility. Both terms mean the same object, and you will meet both in the wild.
RaleyApps live on work items: they create them, react to their events, and add information to their screens.
## Projects, which JSM now calls spaces
Work items live in projects, and a project carries the configuration that shapes everything inside it: work types, workflows, fields, and permissions. Jira Service Management's newer screens call a service project a space. Same container, newer name.
## Request types, the front door of JSM
In Jira Service Management, customers rarely touch work items directly. They pick a [request type](https://support.atlassian.com/jira-service-management-cloud/docs/what-are-request-types-in-a-service-project/) in the portal, such as New employee onboarding, and fill in its form. Each request type is connected to a work type, so a customer-friendly request becomes a normal work item your agents can process. Request types decide what the customer sees; work types decide how the team works.
## Custom fields, where your process lives
Jira's standard fields cover the basics. [Custom fields](https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/) capture what your process needs beyond that, such as a cost center or a delivery date. Apps read and write custom fields through the same field system you see, which is why app data can show up in your boards, reports, and filters.
## JQL and AQL, the query languages
[JQL (Jira Query Language)](https://www.atlassian.com/software/jira/guides/jql/overview) is Jira's structured search. It builds queries that find work items within and across projects, and it powers the filters behind boards, dashboards, and automations.
[AQL (Assets Query Language)](https://support.atlassian.com/jira-service-management-cloud/docs/use-assets-query-language-aql/) is the same idea for Assets, Jira Service Management's inventory of objects such as laptops, rooms, and licenses. If your site manages inventory in Assets, AQL is how you query it. Assets availability depends on your JSM plan; Atlassian's page above is the current record.
## Where each Raley app meets these primitives
| App | Builds on |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| Raley Email Notifications for Jira & JSM | Work item events and conditions that decide who gets notified, when, and with what wording |
| Raley Intake Forms for Jira & JSM | Forms that let people without Jira accounts raise requests that become work items |
| Raley Procurement - Intake & Approval Orchestration for JSM | JSM intake and approval flows that take a request from submission to purchase order |
| Raley Bookman - Asset Reservation for JSM | Reservations raised through the JSM portal and shown on the work item screen |
| Raley Favourites for Jira | One pinned, personal list of the work items you use most |
For what each app does in full, and which one fits your problem, see [Choosing an app](/choosing-an-app).
## What this page does not answer
* How to configure request types, fields, or queries in Jira itself: Atlassian's documentation, linked in each section above, owns that.
* How the apps run on Atlassian's platforms: see [How RaleyApps run on Atlassian](/concepts/how-raley-apps-run-on-atlassian).
* How to get started with a specific app: start at [Get started with RaleyApps](/Get-started-with-RaleyApps).
Questions a page cannot answer belong with a person: reach us through [Support](/support).
***
*Last updated: August 19, 2026*
# Licensing, trials, and billing for Raley apps
Source: https://docs.raleyapps.com/apps/licensing-and-trials
Reference for how RaleyApps apps are priced and billed on Jira Cloud and JSM Cloud: user tiers, free trials, subscription conversion, and cancellation.
This page describes how licensing, trials, and billing work for all 5 Raley apps. Atlassian handles every part of billing: prices, charges, invoices, and cancellation all run through your Atlassian subscription. RaleyApps never receives your payment details.
## How pricing works
| Rule | Behavior |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pricing model | Each app is priced on the number of users of its parent Atlassian product on your site |
| Jira sites with multiple products | Apps for Jira are priced on the maximum user count across your Jira products. Example from Atlassian: Jira with 100 users plus JSM with 80 agents means you pay the 100-user price |
| Billing cycle | The app's cycle always matches the parent product. A monthly Jira subscription means monthly app billing; annual means annual |
| Current prices | Always on each app's Marketplace listing, which is the authoritative source |
| App | Current pricing |
| ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Raley Email Notifications for Jira & JSM | [Pricing tab](https://marketplace.atlassian.com/apps/1214045/raley-email-notifications-for-jira-jsm?hosting=cloud\&tab=pricing\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=licensing-and-trials\&utm_content=email-notifications) |
| Raley Intake Forms for Jira & JSM | [Pricing tab](https://marketplace.atlassian.com/apps/1217327/raley-intake-forms-for-jira-jsm?hosting=cloud\&tab=pricing\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=licensing-and-trials\&utm_content=intake-forms) |
| Raley Procurement - Intake & Approval Orchestration for JSM | [Pricing tab](https://marketplace.atlassian.com/apps/1223409/raley-procurement-intake-approval-orchestration-for-jsm?hosting=cloud\&tab=pricing\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=licensing-and-trials\&utm_content=procurement) |
| Raley Bookman - Asset Reservation for JSM | [Pricing tab](https://marketplace.atlassian.com/apps/1237483/raley-bookman-assets-reservation-for-jsm?hosting=cloud\&tab=pricing\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=licensing-and-trials\&utm_content=bookman) |
| Raley Favourites for Jira | [Pricing tab](https://marketplace.atlassian.com/apps/1220204/raley-favourites-for-jira?hosting=cloud\&tab=pricing\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=licensing-and-trials\&utm_content=favourites) |
## How trials work
| Rule | Behavior |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Starting a trial | Select **Free trial** on the app inside Jira, or **Try it free** on the Marketplace listing. See [Installation](/installation) |
| Trial length | Trials run until one month after the start of your next billing date, per Atlassian's trial policy |
| When the trial ends | The trial converts to a paid subscription automatically unless you cancel before it ends |
| Stopping a trial | In Jira, go to **Apps**, then **Manage apps**, select the app, then unsubscribe |
| Trying again | You can re-enable a trial within its original period. After the period ends, the app can only be subscribed to from **Manage apps** |
**You must cancel before the trial ends to avoid charges.** The conversion to a paid subscription is automatic; this is Atlassian's standard behavior for all Marketplace apps, not something RaleyApps controls.
## Cancelling a subscription
1. In Jira, select **Apps**, then **Manage apps**.
2. Select the app, then **Unsubscribe** or **Uninstall**.
Billing stops with your subscription. For what happens to your data after uninstalling, see the [data security and privacy statement](/policies/data-security-and-privacy).
## Questions this page does not answer
Proration for mid-cycle user changes, refunds, and Enterprise multi-instance billing are governed by Atlassian's subscription terms, not by RaleyApps. Check [Atlassian's billing documentation](https://support.atlassian.com/subscriptions-and-billing/docs/understand-billing-for-cloud-apps/) or [contact support](/support) and we will point you to the right place.
***
*Last updated: August 19, 2026*
# Raley Procurement
Source: https://docs.raleyapps.com/changelog/untitled-page
This page covers feature releases, fixes, and breaking changes for Raley Procurement (formerly Raley Purchase Orders).
For security patches, see the Security Release Notes 2021 and Security Release Notes 2022.
This changelog follows the Keep a Changelog convention: entries are tagged Added, Changed, Fixed, or Security, newest first, and it is maintained by the RaleyApps team after every release.
Maintenance releases with no functional changes are omitted here; the complete raw history is on the Atlassian Marketplace version history.
### Current version: 4.3.0 (July 2, 2026).
## **2026**
### **4.0.0 to 4.3.0 (March 24 to July 2, 2026)**
* **Changed**: the app moved from the 1.0.x-AC version line to 4.x numbering. These releases are platform and maintenance updates with no functional changes
## **2025**
### **1.0.47-AC (March 5, 2025)**
* **Changed**: dashboard and JSM portal view enhancements
## **2024**
### **1.0.44-AC (December 17, 2024)**
* **Added**: add a supplier directly from the purchase order form
### **1.0.43-AC (December 2, 2024)**
* **Added**: multi-currency support
### **1.0.42-AC (November 12, 2024)**
* **Added**: receiving (goods receipt) of purchase orders
### **1.0.41-AC (November 5, 2024)**
* **Added**: Jira dashboard for purchase orders
### **1.0.40-AC (October 31, 2024)**
* **Added**: support for customers and contacts
### **1.0.39-AC (September 13, 2024)**
* **Changed**: color coding for approvers
### **1.0.38-AC (September 2, 2024)**
* **Added**: Sales Quotes. Generate customer-facing sales quote PDFs from Jira/JSM, alongside the purchasing workflow
### **1.0.37-AC (August 29, 2024)**
* **Added**: sharing of requests within an organization
### **1.0.35-AC (June 11, 2024)**
* **Changed**: copying of order lines, PDF improvements
### **1.0.30-AC to 1.0.33-AC (February 1 to March 4, 2024)**
* **Added**: custom fields support, including enumerated custom fields and control over field order
* **Changed**: enforced visibility of the Raley PO web panel
### **1.0.28-AC (January 4, 2024)**
* **Added**: PDF customization
* **Changed**: API update
## **2023**
### **1.0.27-AC (November 6, 2023)**
* **Added**: automatic role assignment
### **1.0.26-AC (October 30, 2023)**
* **Added**: discount functionality
### **1.0.25-AC (October 26, 2023)**
* **Added**: auto-approving budgets
### **1.0.24-AC (October 19, 2023)**
* **Added**: purchase order frame on the JSM create request form
### **1.0.23-AC (October 11, 2023)**
* **Changed**: improved budget lookup
### **1.0.22-AC (October 9, 2023)**
* **Added**: REST API for Products
### **1.0.21-AC (May 18, 2023)**
* **Added**: automatic assignment of custom PO numbers
### **1.0.20-AC (May 17, 2023)**
* **Added**: favourite budgets
### **1.0.17-AC to 1.0.19-AC (March 22 to 27, 2023)**
* **Added**: custom purchase order numbers
* **Added**: company address and logo in the PDF order
* **Changed**: PDF printout modification
## **2022**
### **1.0.16-AC (October 25, 2022)**
* **Added**: accessibility through the JSM portal
### **1.0.14-AC (September 19, 2022)**
* **Changed**: more decimal places supported in prices
### **1.0.12-AC (June 30, 2022)**
Security patch. See [Security Release Notes 2022](/apps/procurement/security-2022).
* **Security**: fixed unauthorized admin page access for JSM customer users
* **Security**: fixed missing authorization on multiple backend REST API endpoints
## **2021**
### **1.0.10-AC (December 15, 2021)**
Security patch. See [Security Release Notes 2021](/apps/procurement/security-2021).
* **Security**: log4j-core upgrade completing the Log4Shell (CVE-2021-44228) remediation
### **1.0.9-AC (December 11, 2021)**
Security patch. See [Security Release Notes 2021](/apps/procurement/security-2021).
* **Security**: critical security patches addressing Log4Shell (CVE-2021-44228), released two days after public disclosure
### **1.0.8-AC (August 23, 2021)**
* **Added**: purchase order PDF generation
### **1.0.6-AC (August 2, 2021)**
* **Security**: fixed Atlassian Connect framework vulnerability
### **1.0.5-AC (July 14, 2021)**
* **Changed**: reporting improvements
### **1.0.4-AC (June 23, 2021)**
* **Added**: Product and Tier approvals
### **1.0.3-AC (June 2, 2021)**
* **Added**: support for department-wide approvers
### **1.0.2-AC (May 19, 2021)**
* **Changed**: roles change logic
## **2020**
### **1.0.0-AC (November 2, 2020)**
* Initial release on the Atlassian Marketplace
## **Questions?**
Can't find what you're looking for? Please contact us at [Support](/policies/service-level-agreement-2).
Last updated: August 19, 2026
# Raley Email Notifications
Source: https://docs.raleyapps.com/changelog/untitled-page-2
This page covers feature releases, fixes, and breaking changes for Raley Email Notifications on Jira Cloud.
This changelog follows the Keep a Changelog convention: entries are tagged Added, Changed, Fixed, or Security, newest first, and it is maintained by the RaleyApps team after every release.
Maintenance releases with no functional changes are omitted here; the complete raw history is on the Atlassian Marketplace version history.
### Current version: 6.2.0 (August 18, 2026).
## **2026**
### **3.1.0 to 6.2.0 (August 4 to 18, 2026)**
* **Changed**: platform and maintenance updates
* **Changed**: required scopes updated in 6.0.0 (August 17, 2026)
### **3.0.0 (July 7, 2026)**
* **Changed**: the app moved to Atlassian Forge. Version numbering jumped from the 1.5.x-AC line as part of this migration
### **1.5.49-AC (January 19, 2026)**
* **Added**: outgoing emails monitoring
## **2025**
### **1.5.48-AC (December 18, 2025)**
* **Added**: notifications to project roles
### **1.5.47-AC (December 1, 2025)**
* **Added**: checking group membership
## **2024**
### **1.5.46-AC (November 5, 2024)**
* **Added**: dark theme support
### **1.5.45-AC (November 4, 2024)**
* **Changed**: improved rendering of web links
### **1.5.43-AC (November 1, 2024)**
* **Changed**: Slack destination configuration externalized
### **1.5.42-AC (October 21, 2024)**
* **Added**: customization of approve and decline buttons
### **1.5.40-AC (May 28, 2024)**
* **Changed**: improved configuration console access
### **1.5.39-AC (February 27, 2024)**
* **Added**: audit for snapshot templates
### **1.5.38-AC (February 20, 2024)**
* **Added**: attach a PDF snapshot of the Jira issue to outgoing notification emails
## **2023**
### **1.5.36-AC (December 4, 2023)**
* **Changed**: improvements in the configurations list
### **1.5.35-AC (November 13, 2023)**
* **Added**: support for Assets fields
### **1.5.33-AC (September 2, 2023)**
* **Added**: support for inlined images
### **1.5.29-AC (January 26, 2023)**
* **Added**: custom References header
### **1.5.28-AC (January 19, 2023)**
* **Added**: custom labels for approval buttons
## **2022**
### **1.5.27-AC (November 10, 2022)**
* **Added**: Gmail OAuth 2 support for sending notifications from your Gmail account
### **1.5.23-AC (August 31, 2022)**
* **Added**: OAuth 2 for Office 365
### **1.5.20-AC and 1.5.22-AC (August 8 and 21, 2022)**
* **Added**: References header support, enabling threaded email conversations per ticket
### **1.5.19-AC (March 12, 2022)**
* **Changed**: configuration console shortcut
## **2021**
### **1.5.18-AC (December 7, 2021)**
* **Changed**: email limitations for trial installations
### **1.5.16-AC (November 27, 2021)**
* **Added**: notifying project organizations
### **1.5.13-AC and 1.5.15-AC (November 9 and 15, 2021)**
* **Added**: retrieving emails of users in an organization, and email retrieval based on account IDs
### **1.5.12-AC (October 28, 2021)**
* **Added**: function for permission checks
### **1.5.10-AC (October 11, 2021)**
* **Added**: additional custom template functions
### **1.5.8-AC (August 16, 2021)**
* **Added**: support for custom email headers
### **1.5.7-AC (July 30, 2021)**
* **Security**: fixed Atlassian Connect framework vulnerability
### **1.5.5-AC (June 4, 2021)**
* **Added**: canned notifications with customisations
### **1.5.3-AC (May 6, 2021)**
* **Security**: critical security patches
### **1.5.2-AC (April 27, 2021)**
* **Security**: fixed Atlassian Connect QSH vulnerability
### **1.5.0-AC (April 22, 2021)**
* **Added**: approve requests via buttons in the email
### **1.4.19-AC (March 10, 2021)**
* **Added**: support for the issue comment updated event
### **1.4.16-AC (February 6, 2021)**
* **Added**: support for notifying CC and BCC recipients
## **2020**
### **1.4.15-AC (October 26, 2020)**
* **Added**: issue Epic fields available in templates
### **1.4.14-AC (October 12, 2020)**
* **Added**: option to send emails separately to each recipient
### **1.4.13-AC (October 11, 2020)**
* **Added**: event processing delay
### **1.4.12-AC (May 21, 2020)**
* **Added**: Quick Start button
## **2019**
### **1.4.8-AC to 1.4.10-AC (October 2019)**
* **Added**: template wizard
* **Changed**: improved thumbnail images in comments, plus the attachThumbnailTargets custom function for inline-referenced image targets
### **1.4.4-AC to 1.4.7-AC (September and October 2019)**
* **Added**: explicit sending to JSD request approvers
* **Added**: additional event type plus project and issue type control for service desk events
* **Added**: additional custom functions
### **1.4.0-AC to 1.4.3-AC (July 2019)**
* **Added**: more fine-grained Jira events
* **Added**: syntax highlighting in the template editor
* **Changed**: required scopes updated
### **1.3.47-AC and 1.3.49-AC (July 1 and 2, 2019)**
* **Added**: OAuth authentication for Slack
### **1.3.44-AC to 1.3.46-AC (March to June 2019)**
* **Added**: recipient and email subject field picker buttons
* **Added**: option to omit the acting user from notifications
### **1.3.43-AC (March 21, 2019)**
* **Added**: application usage statistics
### **1.3.42-AC (March 14, 2019)**
* **Added**: support for ServiceDesk events
### **1.3.40-AC (February 4, 2019)**
* **Changed**: GDPR compatibility
## **2018**
### **1.3.39-AC (December 17, 2018)**
* **Added**: attachment metadata
### **1.3.37-AC and 1.3.38-AC (November 2018)**
* **Added**: mention notifications and UI improvements
* **Fixed**: subject and destination evaluation
### **1.3.34-AC to 1.3.36-AC (September and October 2018)**
* **Added**: convenience fields in notifications
* **Added**: support for rendering issues with version events
* **Changed**: larger subject field
### **1.3.31-AC (August 25, 2018)**
* **Changed**: deployment descriptor URL updated as part of the rebranding from Jirassimo to Raley
## **2017**
### **1.3.1-AC (April 9, 2017)**
* **Added**: sending email to Jira groups
* **Changed**: required scopes updated
### **1.2.26-AC to 1.2.32-AC (March and April 2017)**
* **Added**: template drag and drop, syntax highlighting, test messages, and messenger logging
* **Added**: scheduled notifications preview
* **Added**: email address resolution from template
* **Changed**: minimized fields widget on drag and drop
## **2016**
### **1.2.1-AC (June 24, 2016)**
* **Changed**: required scopes updated
### **1.1.5-AC (April 28, 2016)**
* **Added**: full support for Jira project and version-related events
### **1.1.1-AC (March 4, 2016)**
* **Changed**: required scopes updated
## **2015**
### **1.0.24-AC (December 29, 2015)**
* **Added**: support for Jira Issue Collector metadata access
### **1.0.6-AC (October 15, 2015)**
* **Changed**: major update addressing feedback from our early customers
### **1.0.5-AC (October 8, 2015)**
* **Fixed**: issue with plugin reinstall
### **1.0.0-AC (October 2, 2015)**
* Initial release on Jira Cloud (as Jirassimo)
## **Questions?**
Can't find what you're looking for? Please contact us at [Support](/policies/service-level-agreement-2).
Last updated: August 19, 2026
# Getting started with Raley Favourites
Source: https://docs.raleyapps.com/changelog/untitled-page-3
Install Raley Favourites for Jira, star your first work item, and open your favourites list from the project sidebar, step by step in about 5 minutes.
By the end of this page you will have starred a work item (issue) and opened your favourites list in the project sidebar. Plan for about 5 minutes.
## Before you start
You need:
* A Jira Cloud site with [Raley Favourites for Jira](https://marketplace.atlassian.com/apps/1220204/raley-favourites-for-jira?hosting=cloud\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=raley-favorites-getting-started\&utm_content=raley-favourites) installed. Not installed yet? Follow [Install your app](/apps/Get-started-with-RaleyApps#install-your-app); site admin permission is required for that step, and the rest of this page is not.
* Any work item you can open. Any project, any type.
## Step 1: star a work item
1. Open a work item you use often.
2. Select the more actions menu (**...**) on the work item.
3. Select **Toggle favourite**. It sits at the bottom of the menu, below entries like **Clone** and **Move**.
![Toggle Favourite Menu]( "Toggle Favourite Menu")
The work item is now on your favourites list. Nothing on the work item itself changes, and nobody else's view of it changes either.
## Step 2: open your favourites list
1. Open a project.
2. In the project sidebar, select **Apps**.
3. Under **Your apps**, select **Favourites**.
![Favourites List Sidebar]( "Favourites List Sidebar")
Your list opens, and the work item you starred in step 1 is on it. That is the success state: one starred work item, visible in the list.
## Step 3: use and prune the list
* Add more: repeat step 1 on any work item. Each one appears in the same list.
* Find one fast: when the list grows, use the inline search in the list.
* Remove one: open the work item and select **Toggle favourite** again. The same action adds and removes.
## Next steps
* [What the app is, who it is for, and how it handles your data](/apps/raley-favorites)
* [Add and remove favourites day to day](/apps/raley-favorites/add-and-remove-favourites)
* [The 3 permissions the app requests, and what each is used for](/policies/Application-scopes#raley-favourites-for-jira)
* Stuck on any step? See [troubleshooting](/apps/raley-favorites/troubleshooting), or ask us via the [support page](/support).
***
*Last updated: August 19, 2026*
# Raley Intake Forms Viewer
Source: https://docs.raleyapps.com/changelog/untitled-page-4
This page covers feature releases, fixes, and breaking changes for Raley Intake Forms Viewer, the companion app that embeds Raley Intake Forms in Confluence pages.
This changelog follows the Keep a Changelog convention: entries are tagged Added, Changed, Fixed, or Security, newest first, and it is maintained by the RaleyApps team after every release.
The app ships frequent maintenance releases, which are omitted here; the complete raw history is on the Atlassian Marketplace version history.
### Current version: 1.1.130-AC (July 1, 2025).
## **Cloud**
### **1.1.20-AC (September 16, 2019)**
* **Fixed**: 401 authorization issue
### **1.1.13-AC (December 8, 2018)**
* **Fixed**: 404 error during update
### **1.1.5-AC (August 25, 2018)**
* **Changed**: rebranding from Jirassimo to Raley apps
### **1.1.3-AC (July 26, 2018)**
* **Changed**: updated to use a new server for the app descriptor
### **1.1.0-AC (July 19, 2017)**
* Initial Cloud release
## **Server (discontinued)**
### **1.1.0 (August 25, 2018)**
* **Changed**: rebranding to Raley Intake Forms Viewer
### **1.0.1 (July 13, 2018)**
* **Changed**: updated the plugin to use a new domain as per notice from Atlassian
### **1.0.0 (July 10, 2017)**
* Initial Server release
## **Questions?**
Can't find what you're looking for? Please contact us at `Support`.
Last updated: August 19, 2026
# Raley Bookman
Source: https://docs.raleyapps.com/changelog/untitled-page-5
This page covers feature releases, fixes, and breaking changes for Raley Bookman.
This changelog follows the Keep a Changelog convention: entries are tagged Added, Changed, Fixed, or Security, newest first, and it is maintained by the RaleyApps team after every release.
Maintenance releases with no functional changes are omitted here; the complete raw history is on the Atlassian Marketplace version history.
### Current version: 8.0.0 (July 2, 2026).
## **2026**
### **6.1.0 to 8.0.0 (March 30 to July 2, 2026)**
* **Changed**: platform and maintenance updates; version numbering advanced from the 1.3.x-AC line during this period
### **6.0.0 (March 19, 2026)**
* **Added**: asset context in the booking view
## **2025**
### **1.3.3-AC (August 11, 2025)**
* **Added**: timeline view for bookings
### **1.3.2-AC (July 1, 2025)**
* **Added**: support for specific booking start times and durations
### **1.3.1-AC (April 29, 2025)**
* **Added**: support for JSM Assets
### **1.2.0-AC and 1.3.0-AC (April 22, 2025)**
* **Changed**: required permission scopes updated
### **1.1.0-AC (April 3, 2025)**
* Initial release on the Atlassian Marketplace
## **Questions?**
Can't find what you're looking for? Please contact us at `Support`.
Last updated: August 19, 2026
# Raley Favourites
Source: https://docs.raleyapps.com/changelog/untitled-page-6
This page covers feature releases, fixes, and breaking changes for Raley Favourites.
This changelog follows the Keep a Changelog convention: entries are tagged Added, Changed, Fixed, or Security, newest first, and it is maintained by the RaleyApps team after every release.
Maintenance releases with no functional changes are omitted here; the complete raw history is on the Atlassian Marketplace version history.
### Current version: 2.1.0 (July 1, 2026)
### **Cloud**
### **2.0.0 (February 11, 2026)**
* **Changed**: rebuilt on Atlassian Forge. The app now carries the "Runs on Atlassian" badge, meaning all processing stays inside Atlassian infrastructure
### **1.1.0-AC to 1.1.14-AC (March 2019 to November 2023)**
The original Connect edition, consisting mostly of maintenance releases. Notable versions:
* **Changed**: rebranding to Raley Favourites for Jira (1.1.3-AC, February 1, 2020)
* Initial Cloud release (1.1.0-AC, March 8, 2019)
## **Server (discontinued)**
### **1.1.1 (April 8, 2022)**
* **Security**: security fix for user role and permissions verification
### **1.1.0 (January 31, 2020)**
* **Changed**: rebranding build
### **1.0.1 (March 8, 2019)**
* **Fixed**: compatibility with Jira 8, fixed issue with missing resources
### **1.0.0 (March 8, 2019)**
* Initial Server release
## **Questions?**
Can't find what you're looking for? Please contact us at `Support`.
Last updated: August 19, 2026
# Application scopes
Source: https://docs.raleyapps.com/policies/Application-scopes
Every permission each of the 5 Raley apps requests on the Atlassian Marketplace, listed verbatim per app, with what the app does with that access.
This page lists every permission each Raley app requests from your Atlassian site, app by app. The lists are copied verbatim from each app's Atlassian Marketplace listing (Privacy & Security tab) on August 19, 2026. Permission lists belong to a specific app version, so the listing is always the authoritative source: each section below links to the live tab so you can verify today's list in one click.
## How to read this page
* A permission is what a Jira admin sees and grants when installing the app. It is a declared ceiling, not a log of activity: the list shows the most access the app can request.
* Our listings show permissions in 2 formats. Some apps declare classic site-wide scopes such as Read, Write, and Admin, which Atlassian defines in its [scopes documentation](https://developer.atlassian.com/cloud/jira/platform/scopes-for-connect-apps/). Others declare granular permission statements that describe one capability each. The format follows from how the app integrates with Atlassian; the [platform's concepts page](/how-raley-apps-run-on-atlassian#which-platform-each-raley-app-uses) explains the difference.
* This page covers access permissions only. For where data is hosted, encrypted, and processed, see the [data security and privacy statement](/policies/data-security-and-privacy).
## Raley Email Notifications for Jira & JSM
Email Notifications declares 18 granular permissions. Verify the live list on the [Marketplace Privacy & Security tab](https://marketplace.atlassian.com/apps/1214045/raley-email-notifications-for-jira-jsm?hosting=cloud\&tab=privacy-and-security\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=application-scopes\&utm_content=raley-email-notifications).
**Read access**
* View user information in Jira that the user has access to, including usernames, email addresses, and avatars.
* View user groups.
* View email addresses of all users regardless of the user's profile visibility settings.
* Read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs.
* View project properties.
* Read customer request data, including approvals, attachments, comments, request participants, and status/transitions. Read service desk and request types, including searching for request types and reading request type fields, properties and groups.
* Read Assets objects, their attributes values and details.
* Read Assets object types and their attributes.
* Get list of all Assets object type attributes for a schema or an object type.
* Get list of or details of individual schemas in Assets.
**Write access**
* Create and edit issues in Jira, post comments as the user, create worklogs, and delete issues.
* Create and update project properties.
* Create and edit customer requests, including add comments and attachments, approve, share (add request participants), subscribe, and transition.
**Administration**
* Take Jira administration actions (e.g. create projects and custom fields, view workflows, manage issue link types).
* Create, manage and delete customers and organizations. Add and remove customers and organizations from service desks.
**App runtime**
* Access and interact with your data from outside of Atlassian.
* Access and interact with your data as the logged-in user from outside of Atlassian.
* Read and write to app storage service.
### What Email Notifications uses this access for
Per the permissions justification published on the listing:
| Access | Used for |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Read | Reading issues, projects, and versions from your Jira to build notifications. |
| Write | Adding a comment to an issue when **Audit enabled** is turned on for a notification. The comment body is the text of the notification sent for that issue. |
| Admin | Reading Jira user data and retrieving email addresses of members of specific Jira groups. |
| Email addresses | Retrieving email addresses for accounts in your Jira so notifications can reach them. |
| Act on behalf of a user | Approving or declining JSM tickets from a notification. |
| Delete | Deleting issue properties to manage the app's UI state. Issues themselves are not deleted. |
## Raley Intake Forms for Jira & JSM
Intake Forms declares the 6 classic site-wide scopes. Verify the live list on the [Marketplace Privacy & Security tab](https://marketplace.atlassian.com/apps/1217327/raley-intake-forms-for-jira?hosting=cloud\&tab=privacy-and-security\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=application-scopes\&utm_content=raley-intake-forms).
| Scope | As shown on the listing |
| ------------- | ----------------------------------------------------- |
| Read | Read data from the host application |
| Write | Write data to the host application |
| Delete | Delete data from the host application |
| Project admin | Administer Jira projects |
| Admin | Administer the host application |
| Act as user | Act on a user's behalf, even when the user is offline |
In practice, Intake Forms reads issue and project metadata needed to create issues, creates issues (with attachments) from form submissions, and creates customers in JSM. The scope-by-scope breakdown lives in the [data security and privacy statement](/policies/data-security-and-privacy).
## Raley Procurement - Intake & Approval Orchestration for JSM
Procurement declares 4 site-wide scopes. Verify the live list on the [Marketplace Privacy & Security tab](https://marketplace.atlassian.com/apps/1223409/raley-procurement-intake-approval-orchestration-for-jsm?hosting=cloud\&tab=privacy-and-security\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=application-scopes\&utm_content=raley-procurement).
| Scope | As shown on the listing | What Procurement uses it for |
| --------------- | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Read | View, browse, and read information from Jira. | Reading issue-related information to create and manage the purchasing workflow. |
| Write | Create or edit content in Jira, but not delete content. | Transitioning issues through the workflow. |
| Admin | Administer the Jira site. | Reading project and workflow information to manage PO statuses, and reading Jira user information to handle your organization structure and user rights. |
| Email addresses | Get the email addresses of users. | Sending email notifications to Jira users when their approval of a purchase order is needed. |
## Raley Bookman - Asset Reservation for JSM
Bookman declares 13 granular permissions. Verify the live list on the [Marketplace Privacy & Security tab](https://marketplace.atlassian.com/apps/1237483/raley-bookman-assets-reservation-for-jsm?hosting=cloud\&tab=privacy-and-security\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=application-scopes\&utm_content=raley-bookman).
**Read access**
* Read Assets objects, their attributes values and details.
* Read Assets object types and their attributes.
* Get list of all Assets object type attributes for a schema or an object type.
* Get list of or details of individual schemas in Assets.
* View user information in Jira that the user has access to, including usernames, email addresses, and avatars.
* Read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs.
* Read customer request data, including approvals, attachments, comments, request participants, and status/transitions. Read service desk and request types, including searching for request types and reading request type fields, properties and groups.
**Write access**
* Create and edit issues in Jira, post comments as the user, create worklogs, and delete issues.
* Create and edit customer requests, including add comments and attachments, approve, share (add request participants), subscribe, and transition.
**Administration**
* Take Jira administration actions (e.g. create projects and custom fields, view workflows, manage issue link types).
**App runtime**
* Access and interact with your data from outside of Atlassian.
* Access and interact with your data as the logged-in user from outside of Atlassian.
* Read and write to app storage service.
The permission list mirrors the app's job: Bookman reads your Assets schemas and objects to show what can be reserved, reads and writes JSM requests and Jira issues to handle reservations, and keeps its own data in the Atlassian app storage service.
## Raley Favourites for Jira
Favourites declares 3 permissions, the smallest footprint of the 5 apps. Verify the live list on the [Marketplace Privacy & Security tab](https://marketplace.atlassian.com/apps/1220204/raley-favourites-for-jira?hosting=cloud\&tab=privacy-and-security\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=application-scopes\&utm_content=raley-favourites).
| Permission | What Favourites uses it for |
| ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs. | Reading the issues behind the issue keys you starred, to show your favourites list. |
| Read and write to app storage service. | Storing your starred issue IDs (numeric values only) in Atlassian's app storage. |
| Create and edit issues in Jira, post comments as the user, create worklogs, and delete issues. | Declared, but not used to change your data. Per the published justification, no issue is updated or modified in any way. |
Per the listing justification, no data leaves the Atlassian platform: the app stores only issue IDs, and only in Atlassian storage.
## When permission lists change
Permission lists belong to app versions, and the Marketplace listing always shows the list for the latest version. This page is reviewed against the listings on the date in the footer; if the two ever disagree, the listing wins.
## What this page does not answer
* Where data is hosted, encrypted, and processed, and GDPR terms: see the [data security and privacy statement](/policies/data-security-and-privacy).
* What Connect and Forge are, and which platform each app runs on: see [how Raley apps run on Atlassian](/how-raley-apps-run-on-atlassian).
* How to install an app and grant these permissions: see the [installation guide](/installation).
* Anything about a specific permission on your site: ask us via the [support page](/support).
***
*Last updated: August 19, 2026*
# Data Access & Security Statement
Source: https://docs.raleyapps.com/policies/data-security-and-privacy
How RaleyApps add-ons for Jira and JSM access, process, store, and protect your data, including hosting locations, encryption, and GDPR compliance details.
# **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](mailto: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:
* [**https://www.googleapis.com/auth/gmail.send**](https://www.googleapis.com/auth/gmail.send)
* [**https://www.googleapis.com/auth/gmail.metadata**](https://www.googleapis.com/auth/gmail.metadata)
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](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](https://developers.google.com/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes "https://developers.google.com/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes"), 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](http://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](/policies/service-level-agreement-2)
***
*Last updated: August 19, 2026*
# RaleyApps support service level agreement
Source: https://docs.raleyapps.com/policies/service-level-agreement
The severity levels, first response targets, and coverage rules that apply to every support request across all 5 RaleyApps apps.
This page defines how RaleyApps classifies support requests and how quickly you can expect a first response. It applies to every request, for every customer, across all 5 apps:
* Raley Email Notifications for Jira & JSM
* Raley Intake Forms for Jira & JSM
* Raley Procurement - Intake & Approval Orchestration for JSM
* Raley Bookman - Asset Reservation for JSM
* Raley Favourites for Jira
Contact channels, business hours, and the scope of what support does and does not handle are listed on the [support page](/support). Response targets on this page are measured in business days as defined there.
## Severity levels
Every request is assigned 1 of 4 severity levels. State the impact you are seeing when you raise the request; RaleyApps confirms the severity against the definitions below and tells you if it differs from your assessment.
| Severity | Definition | Examples |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Severity 1 (Critical) | The app is unusable in production for all users and no workaround exists, data is lost or corrupted, or you suspect a security vulnerability. | The app fails to load on every screen; a suspected data exposure. |
| Severity 2 (High) | A core function is broken for many users. A workaround may exist but is not practical for daily use. | A primary feature returns errors for most users; configuration changes do not save. |
| Severity 3 (Medium) | A function is impaired for some users, or behaves incorrectly in specific conditions, and a reasonable workaround exists. | A feature fails only for 1 project or 1 configuration; incorrect display that does not block work. |
| Severity 4 (Low) | A question, a cosmetic issue, a documentation gap, or a feature request. Day-to-day use is not affected. | How-to questions; text or layout glitches; suggestions. |
Suspected security vulnerabilities are always treated as Severity 1 regardless of how many users are affected. Report them through the [support page](/support) channels and do not post details publicly.
## Response targets
| Severity | First response | Update cadence until resolved |
| --------------------- | --------------- | ----------------------------- |
| Severity 1 (Critical) | 1 business day | Every business day |
| Severity 2 (High) | 1 business day | Every 2 business days |
| Severity 3 (Medium) | 2 business days | Every 5 business days |
| Severity 4 (Low) | 3 business days | When the status changes |
These targets meet the response bar Atlassian defines in its Cloud Fortified program for critical issues: a response within 24 hours, 5 days a week.
### What the targets mean
| Term | Meaning |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| First response | A team member has read your request, confirmed the severity, and started diagnosis. An automated acknowledgement does not count as a first response. |
| Business day | A working day within the business hours published on the [support page](/support). Requests raised outside business hours start the clock at the next business day. |
| Update | A substantive note on your request: what was found, what is being tried next, or what is needed from you. |
| Resolved | A fix is released, a workaround you accept is in place, or the behavior is confirmed as working as designed. |
## Resolution
Resolution times depend on the nature of the issue and are targets, not guarantees. For Severity 1 issues, work continues during business hours until a fix or an acceptable workaround is in place. Where a fix requires an app release, the update note tells you the expected release window.
## Escalation
If a request is not progressing or its impact has grown, reply on your existing request and ask for escalation, stating what changed. RaleyApps re-evaluates the severity and adjusts the response handling to match. There is no separate escalation channel; the [support page](/support) channels are the single route in.
## What this page does not cover
| Topic | Where it lives |
| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Contact channels, business hours, and support scope | [Support page](/support) |
| Hosting, data handling, and security practices | [Data security and privacy](/policies/data-security-and-privacy) |
| Platform uptime and availability | Your Atlassian cloud site is operated by Atlassian; platform availability is governed by Atlassian, not by this agreement. |
| Paid support tiers | There are none. Every customer, including evaluators on a trial, receives the same level of support. |
| Legal and contractual terms | The end user license agreement governs; this page describes operational practice, not contractual liability. |
***
*Last updated: August 19, 2026*
# Support Contact
Source: https://docs.raleyapps.com/support
RaleyApps support commitments and response times for Jira and JSM apps, including severity levels, business hours coverage, and escalation procedures.
| Channel | Details |
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Email** | [help@raleyapps.com](mailto:help@raleyapps.com) |
| **Service Portal** | [inversionpoint.atlassian.net/servicedesk](https://inversionpoint.atlassian.net/servicedesk/customer/portal/3) |
| **Community** | [answers.atlassian.net](https://answers.atlassian.net) |
| **Atlassian Marketplace** | [Explore our Atlassian apps](https://marketplace.atlassian.com/vendors/1212475/inversion-point-llc?utm_source=mintify\&utm_medium=productdocs\&utm_campaign=footage\&utm_term=\&utm_content=) |
| **Raley Documentation Feedback** | |
## Business Hours
**8:00am – 9:00pm (GMT+2), Monday through Friday**
Requests submitted outside of business hours will be picked up on the next business day.
## What We Cover
* Product functionality questions
* Issue investigation and resolution
* Workaround suggestions and configuration guidance
* Feedback and feature request collection
## What Is Not Covered
* Training or onboarding sessions
* Scripting or custom programming services
* Issues unrelated to RaleyApps products
***
*Last updated: August 19, 2026*
# Troubleshoot Raley Favourites
Source: https://docs.raleyapps.com/untitled-page-10
Symptoms, likely causes, and fixes for common Raley Favourites for Jira problems: missing Toggle favourite entry, missing Favourites view, and starred work items not appearing.
Work down the symptom that matches what you see. Fixed in one step or not at all? The [support page](/support) is the escalation path either way.
## Symptom index
| Symptom | Jump to |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------- |
| **Toggle favourite** is not in the work item's more actions menu | [Toggle favourite missing](#toggle-favourite-missing) |
| No **Favourites** entry under **Apps** in the project sidebar | [Favourites view missing](#favourites-view-missing) |
| A work item you starred is not in the list | [Starred work item not in the list](#starred-work-item-not-in-the-list) |
## Toggle favourite missing
**Symptom:** you open the more actions menu (**...**) on a work item and there is no **Toggle favourite** entry.
**Likely cause:** the app is not installed on this site, or it is installed but disabled.
**Fix:**
1. Ask a site admin to check **Settings** > **Apps** > **Manage apps** and confirm Raley Favourites for Jira is installed and enabled.
2. Not installed? Follow [Install your app](/apps/Get-started-with-RaleyApps#install-your-app).
3. Reload the work item after the app is enabled and check the menu again.
## Favourites view missing
**Symptom:** the project sidebar's **Apps** section has no **Favourites** entry under **Your apps**.
**Likely cause:** same as above, the app is not installed or not enabled; the sidebar entry ships with the app.
**Fix:**
1. Confirm install state under **Settings** > **Apps** > **Manage apps**, as above.
2. Confirm you are looking inside a project: the list lives in the project sidebar, not on the Jira home screen.
## Starred work item not in the list
**Symptom:** you selected **Toggle favourite** on a work item, but the favourites list does not show it.
**Likely cause:** the star was toggled twice (the same action adds and removes), or the list is filtered by a search term.
**Fix:**
1. Clear the inline search in the favourites list, then look again.
2. Open the work item and select **Toggle favourite** once more, then recheck the list.
3. Still missing? Contact us via the [support page](/support).
## When you contact support
Include these 3 things so the first reply can be a fix:
1. Your site URL and the project where it happens.
2. The work item key you starred.
3. A screenshot of the more actions menu or the favourites list, whichever looks wrong.
***
*Last updated: August 19, 2026*
# Raley Favourites overview
Source: https://docs.raleyapps.com/untitled-page-4
What Raley Favourites for Jira is: a personal favourites list for the work items you keep coming back to, who it helps, how it handles your data, and what it does not try to be.
Raley Favourites for Jira gives you a personal favourites list inside Jira. You star the work items (issues) you keep coming back to, and the app collects them into one list in your project sidebar, with inline search.
New here? [Star your first work item in about 5 minutes](/apps/raley-favorites/getting-started).
## What it does
The app does 2 things, on purpose:
| Capability | How it shows up in Jira |
| -------------------- | ------------------------------------------------------------------------------------------------------------ |
| Star a work item | A **Toggle favourite** entry in the work item's more actions menu adds it to your list, or removes it |
| Your favourites list | A **Favourites** view under **Apps** in the project sidebar lists everything you starred, with inline search |
## Who it is for
The Marketplace listing describes the core case as a "list of favourites issues which you cannot describe with a JQL, but need to access from time to time". If you keep re-finding the same handful of work items through search, boards, or browser history, this app replaces that habit with one click.
## How it handles your data
Raley Favourites runs on Atlassian Forge. It declares 3 permissions, the smallest footprint of the 5 Raley apps, and stores only the numeric IDs of the work items you star, in Atlassian's app storage. No work item data leaves the Atlassian platform.
* [The exact permission list and what each one is used for](/policies/Application-scopes#raley-favourites-for-jira)
* [What Forge means for where your data is processed](/apps/how-raley-apps-run-on-atlassian)
* [Hosting, encryption, and GDPR details for all Raley apps](/policies/data-security-and-privacy)
## What it is not
* Not a shared or team list. The list you build is your own.
* Not a reporting or filter tool. For lists you can describe with a query, use a saved JQL filter; the concepts page on [Jira and JSM primitives](/apps/jira-jsm-primitives) explains JQL.
* Not a watch or notification feature. Starring does not modify the work item, so it cannot add you as a watcher, and nothing in the published feature set sends notifications.
## Pricing and trial
Raley Favourites is paid via Atlassian. Current tiers and the free trial live on the [Marketplace listing](https://marketplace.atlassian.com/apps/1220204/raley-favourites-for-jira?hosting=cloud\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=raley-favorites\&utm_content=raley-favourites), and [Trials, licensing, and billing](/apps/Get-started-with-RaleyApps#trials-licensing-and-billing) explains how trials and billing behave for every Raley app.
## What this page does not answer
* How to install the app and star your first work item: see [getting started](/apps/raley-favorites/getting-started).
* Day-to-day tasks: see [add and remove favourites](/apps/raley-favorites/add-and-remove-favourites).
* Settings, permissions, fields, and API status: see the [reference page](/apps/raley-favorites/reference).
* Quick answers on privacy, storage, and limits: see the [FAQ](/apps/raley-favorites/faq).
* Something not working: see [troubleshooting](/apps/raley-favorites/troubleshooting).
* Anything specific to your site: ask us via the [support page](/support).
***
*Last updated: August 19, 2026*
# Getting started with Raley Favourites
Source: https://docs.raleyapps.com/untitled-page-5
Install Raley Favourites for Jira, star your first work item, and open your favourites list from the project sidebar, step by step in about 5 minutes.
By the end of this page you will have starred a work item (issue) and opened your favourites list in the project sidebar. Plan for about 5 minutes.
## Before you start
You need:
* A Jira Cloud site with [Raley Favourites for Jira](https://marketplace.atlassian.com/apps/1220204/raley-favourites-for-jira?hosting=cloud\&ref=docs.raleyapps.com\&utm_source=docs\&utm_medium=productdocs\&utm_campaign=raley-favorites-getting-started\&utm_content=raley-favourites) installed. Not installed yet? Follow [Install your app](/apps/Get-started-with-RaleyApps#install-your-app); site admin permission is required for that step, and the rest of this page is not.
* Any work item you can open. Any project, any type.
## Step 1: star a work item
1. Open a work item you use often.
2. Select the more actions menu (**...**) on the work item.
3. Select **Toggle favourite**. It sits at the bottom of the menu, below entries like **Clone** and **Move**.
The work item is now on your favourites list. Nothing on the work item itself changes, and nobody else's view of it changes either.
## Step 2: open your favourites list
1. Open a project.
2. In the project sidebar, select **Apps**.
3. Under **Your apps**, select **Favourites**.
Your list opens, and the work item you starred in step 1 is on it. That is the success state: one starred work item, visible in the list.
## Step 3: use and prune the list
* Add more: repeat step 1 on any work item. Each one appears in the same list.
* Find one fast: when the list grows, use the inline search in the list.
* Remove one: open the work item and select **Toggle favourite** again. The same action adds and removes.
## Next steps
* [What the app is, who it is for, and how it handles your data](/apps/raley-favorites)
* [Add and remove favourites day to day](/apps/raley-favorites/add-and-remove-favourites)
* [The 3 permissions the app requests, and what each is used for](/policies/Application-scopes#raley-favourites-for-jira)
* Stuck on any step? See [troubleshooting](/apps/raley-favorites/troubleshooting), or ask us via the [support page](/support).
***
*Last updated: August 19, 2026*
# Add and remove favourites
Source: https://docs.raleyapps.com/untitled-page-6
Add a work item to your Raley Favourites list in Jira, find it again with inline search, and remove it by toggling the favourite off.
This page covers the day-to-day tasks in Raley Favourites for Jira. First time using the app? Start with [getting started](/apps/raley-favorites/getting-started) instead.
## Add a work item to your favourites
1. Open the work item.
2. Select the more actions menu (**...**).
3. Select **Toggle favourite**.
The work item joins your list. Starring changes nothing on the work item itself and nothing in anyone else's view.
## Open your favourites list
1. Open a project.
2. In the project sidebar, select **Apps**, then **Favourites** under **Your apps**.
## Find a work item in a long list
Use the inline search in the favourites list to filter it.
## Remove a work item from your favourites
1. Open the work item.
2. Select the more actions menu (**...**).
3. Select **Toggle favourite** again.
The same action adds and removes: starred becomes unstarred. The work item itself is untouched.
## Result
Your list contains exactly the work items you have starred and not yet unstarred. Something off? See [troubleshooting](/apps/raley-favorites/troubleshooting).
***
*Last updated: August 19, 2026*
# Raley Favourites reference
Source: https://docs.raleyapps.com/untitled-page-7
The complete Raley Favourites for Jira reference: settings, the 3 requested permissions, field behavior, data storage, and API status.
Everything configurable, requested, or stored by Raley Favourites for Jira, on one page. Current as of Cloud version 2.1.0.
## Settings
Raley Favourites has no documented settings screen and no documented admin configuration. Install it, then star work items; no setup step sits between the two in any published material. If a future version adds configuration, this section will list it.
## Permissions and scopes
The app requests 3 permissions, the smallest footprint of the 5 Raley apps. The canonical per-permission list, with what each one is used for, lives on the [application scopes page](/policies/Application-scopes#raley-favourites-for-jira); the Marketplace listing's Privacy & Security tab always shows the list for the latest version.
## Fields
The app creates no custom fields and writes nothing to your work items. Per the published scope justification, no work item is updated or modified in any way.
## Data storage
| Item | Value |
| --------------------- | ------------------------------------------ |
| What is stored | The numeric IDs of the work items you star |
| Where | Atlassian's app storage service |
| What leaves Atlassian | Nothing |
| Platform | Atlassian Forge |
Hosting, encryption, and GDPR details for all Raley apps live in the [data security and privacy statement](/policies/data-security-and-privacy).
## API
No API is documented for Raley Favourites, and no REST endpoints are documented for reading or writing your favourites list. Need programmatic access? Tell us via the [support page](/support) so we can gauge demand.
***
*Last updated: August 19, 2026*
# Raley Favourites FAQ
Source: https://docs.raleyapps.com/untitled-page-9
Quick answers about Raley Favourites for Jira: who can see your list, where it is stored, notifications, limits, and export.
Short answers, with links to the page that goes deeper. Question not here? Ask us via the [support page](/support) and we will answer and add it.
## Can my teammates see my favourites list?
The list is your own. Starring a work item changes nothing on the work item and nothing in anyone else's view of Jira. The app stores your starred work item IDs in Atlassian's app storage, not on the work item.
## Where is my list stored, and does any data leave Atlassian?
In Atlassian's app storage service, as numeric work item IDs only. Nothing leaves the Atlassian platform. The [reference page](/apps/raley-favorites/reference) has the full data storage table, and the [application scopes page](/policies/Application-scopes#raley-favourites-for-jira) lists each permission.
## Does starring a work item notify anyone or make me a watcher?
No. Starring does not modify the work item, so it cannot add you as a watcher, and nothing in the published feature set sends notifications. It only puts the work item on your list.
## Do I need to configure anything after installing?
No. No settings screen or admin setup is documented; install, star, done. The [getting started page](/apps/raley-favorites/getting-started) walks the first 5 minutes.
## How many work items can I star?
No limit is documented. If you hit one in practice, tell us via the [support page](/support).
## Can I export or share my list?
The published feature set has no export or sharing. Your list lives in the **Favourites** view in the project sidebar.
***
*Last updated: August 19, 2026*