Skip to main content
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. 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

Still deciding after the sections below? Contact 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.

​
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 and 5 advantages over the 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 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