Engineering teams see the customers behind their work
Product managers and engineers use Gambit to see who their Jira work is for. On a bug or another software work item, the customer panel lists the accounts linked to it. Each account shows its ARR, health, open deals and renewal date. When a bug is linked to a support request, it carries the requester's account too.
Free on Jira sites of up to 10 users.
Engineering plans the fix a week before the promise
At 2:40 in the Davis sample day, Camila Reyes's fix for Highgate's pickup sync is in QA. It is planned for Nov 17, a week before Claire Avery's Nov 24 promise to Highgate. On paid plans, promises like Claire's are found in customer email that Gambit Mail Sync has captured. Each one a person accepts in the Inbox becomes a Jira work item, linked to the deal and its epic. Atlassian bills Mail Sync separately.
Mail Sync requires an active Gambit subscription.
Capture needs a paid Gambit plan.
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.
See the 2:40 hour at Davis · More on promises · Mail Sync pricing
Davis Hospitality and its people are invented sample data. The hotel and cruise companies are real names used as sample accounts.
An engineer sees who a bug affects and what they pay
An admin adds the customer panel to the software spaces they choose. Revenue impact, a field on work items with linked customers, holds the ARR at stake. Product managers filter Jira search on it to plan by what customers are waiting for.
Delivery starts from the won deal, with a brief
A won deal's owner gets "Closed Won: start delivery" in their Inbox. Start delivery builds the delivery epic from a template, with its first work items. The account and the deal's contacts carry over to the epic. A handoff brief on the epic lists scope, stakeholders, risks and open questions.
For your Jira admin
Free on Standard for sites of 1–10 users: the whole CRM, industry packs and Ask, with about 60 to 100 Ask analyses a month; background capture, summaries and drafts need a paid plan.
Questions and answers
Can engineers see which customers a bug affects?
Yes. In the software spaces where an admin adds it, the customer panel on a bug names each linked customer, with ARR and open deals. Engineers can then plan a fix by who is waiting on it and what they pay.
What does an engineer see on an account they can't open?
The customer panel still names the account, with its tier, revenue and owner. It says "You can't open this account. Ask the owner for access." Each linked account is named and counted, so an engineer knows the fix matters to that customer and whom to ask.
Get on the Gambit mailing list
Gambit is on its way to the Atlassian Marketplace.