How to Show Salesforce Account Tier on a Linear Issue
Linear doesn't show Salesforce account tier or ARR on the issue view by default, and that's true even after you've done the work of linking a customer request to it. Tier, Size, and Revenue are real fields, but they live on the Customer's own dedicated page, one click away from the issue an engineer is looking at. Linear's own documentation is specific about this: those attributes show up on the customer page, populated "automatically if you use the Intercom integration, or can be filled when creating customers manually." The issue itself, per the same docs, shows the request's quote, a link to the source conversation, the requester's name, and a timestamp. No tier, no dollar figure, not on that screen.
You can still get the account's weight in front of engineering without them asking sales, though not by staring harder at the issue. There are two native routes: a custom View that filters or groups by Tier, and Linear's Salesforce package for teams on Enterprise. Look past whether the field exists and each one has a real gap. The View only surfaces a value that's already there; the Salesforce package only fills that value in once.
ENG-482: dual sign-off before archivingWhat Linear ships, and where the line sits
A Linear Customer carries three fields worth knowing about: Tier, Size, and Revenue. They're structured, filterable data, not free text. What they're not is per-issue. One Customer record holds one Tier value, shared across every request that account has ever filed, whether that request is a blocking bug or a nice-to-have.
The path from "field exists" to "engineer sees it while triaging" runs through a custom View. Linear's own documentation walks through this exact setup, recommending you "create a view of issues with requests from Enterprise customers ('Tier' property from Intercom), where each issue has at least 20 requests." Build that view, pin it, and Tier becomes something a triager filters or sorts by instead of a fact locked on a separate page. That's a real, working answer. It's also a second screen someone has to remember to open, sitting apart from wherever the team plans its sprint.
The two ways Tier gets filled in
Before a view can filter on Tier, something has to put a value in it. Linear gives you two native paths, and it's worth being precise about what each one does, because "the field exists" and "the field stays correct" are different claims.
- The Intercom integration. If support runs through Intercom, Tier, Size, and Revenue sync onto the matching Customer automatically. This is the cleanest native path, and it requires nothing beyond having Intercom connected already.
- Salesforce, mapped by hand, on Enterprise. Linear's Salesforce integration is sold as an add-on to Linear's Enterprise plan. An admin sets up field mapping in Settings, Customer requests, choosing which Salesforce Account property feeds which Linear Customer attribute, limited to Owner, Tier, Status, Revenue, and Size. Once mapped, "creating issues from a Salesforce case will create new Customers in Linear as needed" and pulls the mapped fields in at that moment.
The second path is where teams get surprised. The docs describe the mapping firing when a Customer gets created from a case, not as a standing, continuous sync. Nothing in Linear's documentation promises that a tier change in Salesforce next quarter, a renewal, an upgrade, a churned-and-won-back account, updates the Linear Customer that already exists. The value that lands on issue creation is the value that's there until someone touches it again by hand.
Bridget's account tier goes stale at Briarcombe
At Briarcombe, a work order and maintenance software vendor for commercial office building managers, support tickets come in through Salesforce Cases and engineering tracks everything in Linear. Bridget Vantassel owns roughly ninety of those accounts as her customer success book. Eight months ago, when Briarcombe turned on the Salesforce package, Bridget mapped Tier__c on the Account object straight to Linear's Tier attribute, so any case that became an issue would carry the account's tier along with it.
In November, a mid-market account, Overbrook Commercial Group, filed a case asking for a way to bulk-approve recurring work orders instead of clicking through each one. Bridget created the Linear issue from the case, and it landed with Tier: Growth, accurate at the time. Two months later, Overbrook signed an upsell that moved them to Briarcombe's top tier, and nobody went back into the open Linear issue to update it.
Jonah Petrosky, engineering lead, in the #eng-planning Slack channel: Ranking next sprint's backlog and ENG-338 (bulk-approve work orders) is tagged Growth tier, so it's sitting behind two Enterprise asks. Is that still right?
Bridget, replying: No, that's stale. Overbrook upgraded to Enterprise in December. The Linear field never got touched because nothing pushed the update after the issue was already created.
Jonah re-ranked the issue by hand once he knew, but the correction depended on Bridget happening to see the message and remembering the account's history. The mapping had done its job exactly once, at creation, and then gone quiet.
Where the native setup stops holding up
None of this is a bug in Linear. The docs never promise a live, ongoing sync from Salesforce, and treating the mapping as one is the actual mistake, not the tool. Three things break down in roughly this order as volume grows:
- Tier is a snapshot, not a subscription. It's accurate the moment an issue is created and stale the moment the account's status changes after that, with nothing flagging the gap.
- The custom View is a second surface. It shows tier when someone opens it, but a triager working straight from the issue list or a Slack notification never sees it unless that habit is built and maintained.
- Duplicate Customer records break the filter quietly. If a support rep and an account manager each create a Customer entry for the same company at different points, one might carry the current tier and the other the old one, and a View filtered on Tier only catches whichever record it's looking at.
Past a few dozen open requests a month, keeping tier current by hand is the same job as keeping any spreadsheet current by hand: it works until the person who remembers to do it gets busy, and there's no way to tell from inside Linear which issues are already wrong.
Where Modem keeps tier current
This is the gap Modem works on, and since we build Modem, weigh the rest of this section with that in mind. Modem's Salesforce integration syncs accounts, contacts, opportunities, and users, read-only by design, so account and opportunity data stays current instead of sitting as whatever value got copied in at issue creation. Modem's Linear integration creates issues with the customer quotes and user stories included, not a bare one-line title, and links incoming feedback to existing issues instead of filing the same bug twice. Because the account sits in the same graph as the request, an engineer working a topic tied to a Linear issue can see which account raised it and pull up that account's current Salesforce standing without opening Salesforce directly, checking a separate View, or pinging Bridget in Slack.
It doesn't replace Linear's Customer Requests feature or the Salesforce package for teams already relying on them; it removes the part where account context is only as fresh as the last person who remembered to update it, so a triager can check an account's current standing against whatever tier is sitting on the Linear issue. For the fixed-field limits on the request object itself, how to add custom fields to a Linear customer request covers what Linear's schema does and doesn't hold. For teams weighing whether a Salesforce contract is worth it at all for this specific problem, can Linear customer requests weight feedback by revenue without Salesforce walks through the free paths first.
The smallest version worth setting up this week
If you're not ready to touch the sync question yet, build one pinned View filtered to your top two Tiers, and put a line in your renewal-handoff checklist that says "update the Linear Customer tier" next to "update the CRM." Neither fix is glamorous, but the View makes tier visible to whoever opens it, and the checklist line is the cheapest way to keep Jonah's next backlog ranking from running on a number that stopped being true two months ago.
