このページはまだ翻訳されていないため、英語で表示しています。

Release notes

What's new in Rainbook and Rainbook Mail Sync, newest first, with a dated entry for every version we release.

Rainbook 1.0 · Tue 15 Dec 2026

Rainbook is on the Atlassian Marketplace: a CRM that lives in Jira, with your customers and the revenue behind every issue in plain sight.

New

• Your CRM as Jira work. Deals, leads, follow-ups, renewals, accounts, contacts, email threads and meetings are Jira work items in three spaces, with JQL, permissions, Automation, dashboards and the Jira mobile app.
• A guided setup. The setup wizard previews every space, field, workflow, scheme, group and security level before it changes anything, and asks one question about who sees customers, deals and email.
• Your whole team uses Rainbook from day one. Everyone who can open the CRM space is a Rainbook user, with no group to fill in, and your Jira admins run it. Setup asks Who uses Rainbook? with Everyone in Jira or Limit Rainbook to a group. Earlier sites can switch in Settings › Access › Who uses Rainbook, with a confirmation naming who gains or loses access; on Jira Free use Run setup again. With the Regulated pack, use stays group-only and only rainbook-admins members administer Rainbook.
• The Rainbook workspace. Home with today's meetings and follow-ups, slipped deals and at-risk renewals, plus the Inbox, Pipeline, Accounts, Contacts, Conversations with email search, Renewals, Reports and a full record page, with a fast local cache and the ⌘K command palette. See the workspace.
• Ask. Ask a question in plain words, such as "Which renewals are at risk this quarter?", and get a chart you can refine and save to a Jira dashboard.
• The customer panel. Software and service work items show the customers they affect and the revenue waiting on them.
• Rainbook fields across Jira. Account, People, Revenue impact and Health show full names in software and service work items, search, the mobile app and CSV exports, plus dashboard gadgets for classic and new dashboards.
• Work that knows the customer. Revenue impact on linked software and service work items, support requests and bugs linked to their accounts, and renewal risk from support signals.
• Start delivery. When a deal is won, Start delivery creates its delivery epic or space from a delivery template, with the first work items and a handoff brief, and Undo for 7 days. Anyone who can't create the work proposes the handoff instead.
• Promises become work. A promise in a customer email becomes a tracked work item linked to the engineering epic that delivers it, and turns At risk when the epic slips.
• Rainbook agents. Capture, Research, Follow-up, Deal desk, Renewal and Handoff agents work your pipeline board in the open, and every change waits for a person.
• AI that works with you. Record and deal summaries with next steps, health scores with reasons, drafted follow-ups, duplicate detection with one-pair merge, and agent proposals you apply with one click and Undo, or send to the record's owner as an Approval request. Show sources lists the records and emails behind every AI result.
• The Rainbook agent in Rovo. Ask Rovo about your pipeline. Each person sees exactly what Jira lets them see. Claude and ChatGPT, through Atlassian's MCP server, are coming soon.
• Private deals. Make a deal private to the people you choose; its email and meetings follow it, everywhere Jira checks permissions.
• Import. Bring in Salesforce, HubSpot and Pipedrive exports with a dry run, duplicate matching, email history and Undo for 14 days.
• Industry packs. SaaS and Professional services, plus Life sciences, government contractors and legal packs in early access.
• Admin settings. Overview with Copy diagnostics, Plan and usage, Adoption, Packs, Delivery templates, New stages, Mail, Linking, Integrations, Privacy and data with privacy requests, Activity history (13 months, or as long as you choose on Advanced), AI and Rovo, and AI budget.
• Admin notifications. One bell in the header lists what needs an admin, such as setup, storage, AI use, Mail Sync and the subscription, each with its fix, Done and Snooze. A new pipeline stage someone adds in Jira is one question away from counting in every board and total.
• Reporting history. From the day you install, Rainbook records changes to deal amounts, dates, probability, owner and forecast category, and a daily snapshot of open deals and renewals. Deals carry a Forecast category: Commit, Best case, Pipeline or Omitted.
• Everyday essentials. Multi-currency reporting, time zones, payment card and Social Security number masking, export to CSV or an Excel workbook, and a nightly archive of Rainbook's data into Jira.
• Editions. Free for sites of 1 to 10 users, Standard, and Advanced with a larger AI budget, activity history kept as long as you choose and higher limits. Advanced also offers the optional Regulated pack in early access.

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.

Rainbook Mail Sync

• Email and calendar capture from Microsoft 365 and Google Workspace, with full message bodies, every attachment and inline images, onto the right accounts and deals. Microsoft 365 users connect their own mailbox wherever their IT allows it, or IT connects everyone; Google Workspace capture is connected by the IT admin; capture is labelled beta; personal Gmail opens after Google's review, with a waitlist.
• Capture conversations with new prospects. Threads someone on your team starts with, or replies to, an outside person are captured from their own sent copy. When someone on the team replies, up to 6 earlier messages from the 30 days before come with it. Choose Create account and contact, Create contact at <Account> when the domain's Account exists, or Open lead when the person is an open Lead. Open Leads match by email only, never by company domain. Mail with more than 100 outside recipients is skipped unless a known party (a Contact, an Account's domain or an open Lead) is on the thread, or the thread is already being followed. Exactly 100 outside recipients is within the limit. Mailing-list headers still mark mail as bulk unless the sender is an exact Contact or open Lead. Team-organised meetings with outside guests are captured even before the guests are in Rainbook: the mailbox owner organised, or a colleague organised and the owner accepted or tentatively accepted. Meetings can have up to 150 attendees; 151 or more are skipped. To log internal email, choose the customer record in the sidebar, then Log. See Mail Sync for backfill, privacy and capture exclusions.
• Gmail and Outlook sidebars. See the contact, account, owner and open deals beside every email, log a thread, create a deal or follow-up, and draft a reply.
• Private threads. Make any thread visible only to you and the people Jira allows (by default, the owner and members of rainbook-admins), with one click, from Rainbook or the sidebar.

In Rainbook Beta now

In Rainbook Beta now, and in Rainbook from January.

• Customers in Rovo Search. Accounts and deals in the Teamwork Graph, so Rovo answers with the cited deal and requests.

Coming next

Planned for January and February 2027: plain-English automations, meeting prep, a bulk merge queue, agents that update many records at once, Customer Service Management sync, a customer panel for Jira Service Management organizations, Rainbook JQL functions, importing straight from Salesforce and HubSpot, company enrichment with your own provider key, and self-serve and personal Gmail capture after Google's review.