Fields and JQL reference

Every field Gambit 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

Gambit 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, Gambit 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), Gambit'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.

The CRM space also holds one Gambit Archive work item that only members of rainbook-admins can open.

Gambit's own fields

Four fields belong to Gambit. You can search them in JQL and add them to boards and filters for software and service work items.

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:

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 Gambit sets up

Gambit 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.

Account key holds the account's key (for example RBDIR-12) on every Gambit 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.

Move records to another account with Automation

To move a contact, deal or lead to another account from Jira Automation, a bulk change, a CSV update or the REST API, set one of two fields:

• Account key (simplest): in Automation's Edit work item action, choose Account key and enter the new account's key, for example RBDIR-12. Gambit sets the Account field to that account.
• Account: in the same action's More options › Additional fields, enter all four values of the account, where id is the account's work item ID and name its summary:

{ "fields": { "Account": { "v": 1, "key": "RBDIR-12", "id": "10123", "name": "Acme" } } }

Either way, Gambit then moves the record as its own editors do: the old account's link is removed, a contact's employment moves to the new account, and who can see the record follows the new account. A bulk change moves its records over the next few minutes; one too large for the hour's Jira allowance finishes in the next hour.

Gambit refuses a key or value that isn't an account in the Directory space, a cleared Account key, and a cleared Account where the edit screen requires the field, and puts back the account the record keeps.

Properties you can search

Gambit also keeps search-ready properties on its work items. Search them by the aliases below.

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 < 70

Deals 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 DESC

Email 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 key on every item.
• Gambit'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.
• Gambit's search properties stay on your work items, but searching by them stops until Gambit is installed again.

The Admin guide lists everything you keep.