Rainbook

Rainbook in your Jira work

Rainbook brings the customer and the revenue into the Jira work your teams already do: bugs, support requests, epics and dashboards.

The customer panel on every work item

Add Rainbook's customer panel to your software and service spaces, and each work item shows which customers it touches: each account by name, its tier, revenue, health and top reason, open deals and renewal date.

  • Add customer request links an account (and, if you like, one of its open deals) to a work item in a click, up to 100 accounts per item.
  • Every linked account is named and counted. If you can't open an account, the panel still shows its name, tier, revenue and owner, with "You can't open this account. Ask the owner for access."

Revenue impact in JQL and filters

Each software or service work item with linked customers gets a Revenue impact field: the revenue at stake, open pipeline, revenue at risk, the top tier and the nearest renewal, for example "USD 310000 ARR at stake · Acme Corp, Globex +1". Search and filter on it in JQL, and sort any search by the money at stake with ORDER BY frArr DESC, so you can plan by what customers are waiting for. Sorting by the column header orders work items by their linked accounts, not by amount.

"Revenue impact.arr" > 100000 AND statusCategory != Done ORDER BY frArr DESC
"Revenue impact.renewalDate" <= endOfDay("+90d")
"Revenue impact.accountNames" ~ "acme"

Revenue impact stays current on its own. After a big change, such as an import or a new reporting currency, it refills gradually (about 120 work items a day on paid plans and 16 on the free tier) and never holds back a change's first 100 work items. While a work item waits, its panel says "Updating" with an estimate, and totals built from Revenue impact say "Still filling", so a number is never quietly incomplete.

The full list of fields and searches is in the Fields and JQL reference.

Support requests linked to customers

When a request or bug is created outside Rainbook's own spaces, Rainbook links it to the right account by itself:

  • By the requester's email, matched to a contact or to an account's domain.
  • By Jira Service Management organization, once you map your organizations to accounts in the setup wizard. New organizations show on Settings › Linking as unmapped.
  • Bugs inherit accounts. Link a bug to a customer's request and the bug picks up that customer too.

The panel always says why: "Linked to Acme: reporter is jane@acme.com". If it's wrong, click Change to pick another account (and optionally "Always link @domain to this account"), or Not a customer (and optionally "Never link this domain"). Corrections stick through every later check. Requests Rainbook can't place wait in the Inbox under Unlinked requests, and Settings › Linking lets you keep Rainbook out of spaces you choose.

At setup you can link the last 30 or 90 days of requests and bugs in one go. Rainbook uses requesters' email addresses to match support requests to your customers.

Renewals and health

Every account has a health score from 0 to 100: Healthy (70 and above), Watch (40 to 69) or At risk (under 40). It is built from the signals your teams already create: support volume and its trend, high-priority requests, SLA breaches, open bugs and their age, how fast your team replies, days since the last conversation, the time to renewal and how long expansion and renewal deals have sat in their stage. On paid plans Rainbook's AI writes the reasons in plain words; on the free tier the top signals are shown as they are, such as "3 SLA breaches in 30 days".

  • Renewals open on time. With the SaaS pack (or any pack that uses renewals), Rainbook creates a Renewal work item 120 days before each account's renewal date (you can choose 30 to 365), with the owner, amount and close date filled in.
  • Owners hear about trouble. When an account's health falls under 40, or drops 15 points in a week, it shows on Home and in Renewals, and the owner gets one Jira notification with the top reason, at most once a week per account.

Deal-to-delivery

When a deal moves to Closed Won, Rainbook offers the handoff to delivery with the pack's template ready: an epic in your delivery space, or a new space from a template, with the work already laid out.

  • Start delivery runs it at once if you can edit everything involved. If you can't, Propose handoff sends it to someone who can, as an approval request.
  • What carries over: the account, the deal's contacts with their roles, the amount if you want it, the SOW, quote and order files, line items, and the pack's commercial fields you map. The epic links back to the deal.
  • A handoff brief lands as a comment on the epic: scope, commitments, stakeholders, risks and open questions. On the free tier it lists the deal's fields, people and recent threads.
  • Progress comes back. The deal shows the delivery epic's progress and any slipping dates.
  • Undo handoff removes what the handoff created, for 7 days.

A deal closed in plain Jira gets the same offer: after 15 minutes the deal's owner finds "Closed Won: start delivery" in their Inbox. The Professional services pack ships two delivery templates and the SaaS pack one; Rainbook admins edit them on the Delivery templates page.

Promises and Shipped for you

A promise a rep makes in an email, such as "EU data residency by 15 January", becomes a Commitment work item linked to the deal and to the epic that delivers it. The engineering lead sees on the epic who was promised what, by when, and for which deal. If the epic's date slips past the promise, the Commitment turns At risk and the owner hears about it. When the work ships, each account owner who asked for it gets a drafted customer note to approve, and the promise is marked Kept.

Dashboards: widgets and gadgets

Put Rainbook reports and saved views on any Jira dashboard:

  • On new Jira dashboards, add the Rainbook report and Rainbook list widgets. The report widget comes with a preset, "Revenue waiting on this team's work", that names each account with its revenue and the work it is waiting for.
  • On classic dashboards, the Rainbook report and Rainbook list gadgets do the same.

Each viewer sees the results their own permissions allow, so one shared dashboard works for the whole company. When a viewer's result leaves records out, the widget says so, for example "Excludes 1 deal you can't open". Set a refresh interval of 15, 30 or 60 minutes, and click any bar or row to open the records behind it. Reports run on every plan, the free tier included.

Automation templates and actions

Rainbook's packs include Automation rule templates you import into Jira Automation, for example raising the priority of a bug when the revenue waiting on it passes $100,000. They run once a day by default (hourly if you choose), only touch work items that need a change, and each template says how many Automation steps it uses per run and per month.

The Link to customer account Automation action links a work item to an account from any rule, or finds the account from the requester when you leave it blank. More Rainbook actions (recompute health and revenue impact, offer a delivery handoff, promote a person to a contact, and log activity on an account or deal) arrive in January.

Rainbook's own AI, capture and background jobs are included in your subscription and use neither Rovo credits nor Automation steps. The Rainbook agent in Rovo, Rovo Studio agents that use Rainbook's tools, and Automation rules built from Rainbook's templates or actions use your Atlassian allowances: Rovo credits from 3 Dec 2026, and Automation steps from your first renewal on or after 3 Dec, shown per rule in your admin Usage tab.

In Rainbook Beta now, and in Rainbook from January.

Rainbook publishes your accounts and deals to Atlassian's Teamwork Graph, so you can ask Rovo Chat what is at stake with a customer before a renewal and get an answer that cites the deal, the requests and the promise. Private records and private deals stay out of the graph, and so do email and meetings; Rovo still finds them for the people Jira lets see them, through the Jira work items themselves.