RainbookEsta página aún no está traducida, así que se muestra en inglés.
Fields and JQL reference
Every field Rainbook adds to Jira, the properties you can search, and ready-to-use JQL for finding customers, deals, email and revenue by name.
Search by name
Rainbook stores names, not just codes, so you can find people and companies the way you talk about them. Accounts show as "Acme Corp (RBDIR-12)" and people as "Jane Doe, Raj Patel +2" everywhere Jira shows a field: software and service work items, search results, the Jira mobile app and CSV exports.
Account.name ~ "acme"
People.names ~ "jane doe"
"Revenue impact.accountNames" ~ "acme"
project = RBDIR AND type = Contact AND summary ~ "jane doe"An Account's summary is the company name and a Contact's summary is the person's full name, so plain Jira text search finds them too. When an account or contact is renamed, Rainbook updates the name on every work item that refers to it within 24 hours.
If your site already had a field called "Account" (Tempo adds one, for example), Rainbook's field is named "Customer account": write "Customer account".name ~ "acme".
Spaces and work types
The setup wizard creates three spaces. These are the default keys; yours may differ if you chose others.
| Space | Default key | Work types |
|---|---|---|
| CRM | RBCRM | Deal, Lead, Follow-up, Renewal, Commitment, Approval request, plus pack types such as Quote, SOW, Bid and Matter when you apply a pack |
| Directory | RBDIR | Account, Contact |
| Activity | RBACT | Conversation (one per email thread), Meeting |
The CRM space also holds one Rainbook Archive work item that only members of rainbook-admins can open.
Rainbook's own fields
Four fields belong to Rainbook. You can search them in JQL and add them to boards and filters for software and service work items.
| Field | On | JQL |
|---|---|---|
Account | Deals, leads, follow-ups, renewals, contacts, Conversations, Meetings, and work items in software and service spaces you add it to | Account.key = RBDIR-12, Account.name ~ "acme", Account.tier = Enterprise, Account.arr > 50000 |
People | Deals, leads, follow-ups, renewals, Conversations, Meetings | People.contacts = RBDIR-88, People.names ~ "doe", People.roles = champion, People.contactRoles = "RBDIR-88:champion", People.primary = RBDIR-88 |
Revenue impact | Software and service work items with linked customers | See below |
Health | Accounts, deals, renewals | Health < 40 |
People roles are champion, economic-buyer, decision-maker, influencer, user, blocker and other (packs may add more). Health runs from 0 to 100: Healthy is 70 and above, Watch is 40 to 69, At risk is under 40.
Revenue impact holds the money at stake and every linked account:
| What | JQL |
|---|---|
| Revenue of the linked accounts | "Revenue impact.arr" > 100000 |
| Open pipeline of those accounts | "Revenue impact.pipeline" > 0 |
| Revenue at accounts under 40 health | "Revenue impact.atRiskArr" > 0 |
| Linked accounts | "Revenue impact.accounts" = RBDIR-12, "Revenue impact.accountNames" ~ "acme" |
| Number of linked accounts | "Revenue impact.accountCount" >= 3 |
| Highest tier | "Revenue impact.topTier" = Enterprise |
| Nearest renewal | "Revenue impact.renewalDate" <= endOfDay("+90d") |
| Customer requests | "Revenue impact.requests" >= 2 |
| Last refreshed | "Revenue impact.asOf" >= -7d |
Amounts are in your site's reporting currency. To sort by the money at stake, use ORDER BY frArr DESC (or ORDER BY "Revenue impact.arr" DESC); sorting by the Revenue impact column itself orders work items by their linked accounts, not by amount.
Jira fields Rainbook sets up
Rainbook also creates ordinary Jira fields, which you search like any other field (for example "Close date" <= endOfMonth() or Tier = Enterprise). Owner is Jira's Assignee field.
| Work type | Fields |
|---|---|
| Account | Domain, Other domains, Tier, ARR, Currency, Renewal date, Industry, Employees, Account team, Next step, Rainbook summary |
| Contact | Email, Other emails, Phone, Mobile, Title, LinkedIn URL, Do not contact, Account key |
| Deal | Amount, Currency, Close date, Probability, Forecast category, Loss reason, Next step, Rainbook summary, Account key, Shared with |
| Lead | Lead company, Lead email, Lead phone, Lead source, Disqualify reason |
| Renewal | Amount, Currency, ARR, Renewal date, Probability, Forecast category, Loss reason |
| Commitment | Promised date, Source quote |
| Conversation | Sent at (latest message), First sent at, Direction, Message count, Capture source |
| Meeting | Meeting start, Meeting end, Join link, Location, Capture source |
| Approval request | Approval kind, Approvers, Requested by, Expires at, Reject reason |
| Imported records | Source system, Source ID, Original created |
Account key holds the account's key (for example RBDIR-12) on every Rainbook work item that refers to an account, so "Account key" ~ "RBDIR-12" works in any search. Shared with lists the people on a private deal.
Properties you can search
Rainbook also keeps search-ready properties on its work items. Search them by the aliases below.
| Alias | Finds |
|---|---|
frType | The Rainbook record type: deal, lead, renewal, conversation and so on |
frAccount | Every Rainbook item for an account |
frContacts | Items that involve a contact |
frDeals, frPrimaryDeal | Items linked to a deal |
frMergedInto | Records merged into another record |
frSourceId | A record's ID in your old CRM |
frEmail | A contact by email address |
frContactDomain, frEmployer | Contacts by email domain or by the account they work for |
frDomain | An account by web domain |
frJsmOrg | The account mapped to a Jira Service Management organization |
frHealth, frHealthBand | Health score, and band healthy, watch or at-risk |
frArr, frPipelineValue, frAtRiskArr | Revenue impact amounts |
frImpactAccounts, frTopTier | Revenue impact accounts and top tier |
frThreadEmail | Every email thread with a person |
frPrivate | Threads someone made private ("true") |
frThreadKey, frRootMsg, frProviderThread | A thread by its mail identifiers |
frEventKey | A meeting by its calendar identifier |
frProposalKind, frTargets | Approval requests by kind and by the records they change |
frImportRunId, frImportBatchId | Everything one import created |
frHandoffRunId | Everything one delivery handoff created |
On Rainbook Beta the same aliases start with frb instead of fr, for example frbArr and frbEmail.
Example searches
Customers and people:
frEmail = "jane@acme.com"
frDomain = "acme.com"
project = RBDIR AND type = Account AND frHealthBand = "at-risk" ORDER BY ARR DESC
project = RBDIR AND type = Account AND "Renewal date" <= endOfDay("+90d") AND Health < 70Deals and pipeline:
project = RBCRM AND type = Deal AND statusCategory != Done AND Account.name ~ "acme"
project = RBCRM AND type = Deal AND People.roles = champion AND "Close date" <= endOfQuarter()
frAccount = RBDIR-12 ORDER BY updated DESCEmail and meetings:
frThreadEmail = "jane@acme.com" ORDER BY "Sent at" DESC
project = RBACT AND type = Conversation AND Account.name ~ "acme" AND "Sent at" >= -14d
project = RBACT AND type = Meeting AND "Meeting start" >= startOfDay() AND "Meeting start" <= endOfWeek()Revenue on product and support work:
"Revenue impact.arr" > 100000 AND statusCategory != Done ORDER BY frArr DESC
project = SUP AND "Revenue impact.topTier" = Enterprise AND priority in (High, Highest)
type = Bug AND "Revenue impact.accountNames" ~ "acme"Replace RBCRM, RBDIR, RBACT and SUP with your own space keys. Searches return only the work items you can open, as everywhere in Jira.
Comments on email threads
Each captured message is a comment on its Conversation, carrying the sender, recipients, sent time, a short preview and the attached files. Comment properties aren't searchable in JQL; search the thread instead, by participant with frThreadEmail or by text with text ~ "renewal".
If you uninstall
- Jira's own fields, comments, attachments, links, statuses and filters stay, and so does
Account keyon every item. - Rainbook's four fields (Account, People, Revenue impact and Health) are app fields: their values disappear on uninstall and come back if you reinstall within 30 days.
- Rainbook's search properties stay on your work items, but searching by them stops until Rainbook is installed again.
The Admin guide lists everything you keep.