Color-Coded Customer Tiers
Immediately spot high-priority or sensitive accounts at the top of every ticket so agents triage with confidence on the very first reply.
Stop switching tabs between Jira and your CRM to figure out who just opened a ticket. Customer Context Card surfaces customer tiers, custom fields, shared JSM organization notes, and recent tickets directly in the Jira Service Management sidebar.
customer_id
Text
sla_tier
Dropdown
crm_url
URL Link
notes
Multi-line
Replace scattered spreadsheets and slow CRM lookups with clean, structured context directly inside Jira Service Management.
Immediately spot high-priority or sensitive accounts at the top of every ticket so agents triage with confidence on the very first reply.
Define up to 15 customer fields and 15 organization fields directly in Jira Admin Settings — reorder, rename, or remove fields in seconds.
Language-agnostic detection automatically reads the linked Jira Service Management Organization and displays shared contract plans, account managers, and company notes across every employee's tickets.
Instantly view up to 5 recent tickets from the same reporter with live status lozenges and 1-click navigation — spot repeat incidents before asking redundant questions.
Onboard up to 500 customer records per paste with automatic comma (,) or semicolon (;) detection, quoted values, and Jira email matching processed in resilient batches.
Toggle whether support agents can edit profiles or lock edits strictly to Jira Administrators. Erase any stored customer or organization record permanently with 1-click GDPR / Swiss FADP deletion.
No external account creation, no API keys to rotate, and no third-party connectors to maintain.
Add Customer Context Card to your Jira Cloud site in one click. Everything provisions automatically inside Atlassian Forge.
Open Settings → Apps → Customer Context Card Settings to define your custom customer/org fields and optionally paste your existing CSV export.
Open any Jira or JSM issue and click Customer Info in the sidebar. Agents see tiers, SLAs, CRM links, org notes, and ticket history instantly.
Designed for security-conscious IT, finance, healthcare, and Swiss/EU enterprises that cannot send customer metadata to third-party SaaS backends.
manifest.yml. Customer records never leave Atlassian.
Only 3 least-privilege scopes — zero write access to your Jira tickets or users.
Paid transparently through Atlassian Marketplace with a 30-day free trial and automatic volume discounts.
Up to 10 licensed Jira agents
11–100 licensed Jira agents
101+ licensed Jira agents
Slide to match your Jira user tier for an instant Atlassian Marketplace estimate.
No. Customer Context Card is built 100% natively on Atlassian Forge (nodejs24.x + UI Kit) and stores all profiles exclusively in encrypted Atlassian Forge Storage (@forge/kvs). There are no external backends, third-party databases, or egress domains in the app manifest.
Yes. The issue context panel appears on any Jira Cloud issue with a reporter. On Jira Service Management tickets that belong to a JSM Organization, the shared Organization section is automatically detected and displayed as well.
Yes. Inside Jira Settings → Apps → Customer Context Card Settings, simply uncheck Allow support agents to edit customer and organization fields. Agents will see a clean read-only card while Jira Administrators retain full edit and CSV import control.
Our RFC-4180 CSV parser automatically detects both comma (,) and semicolon (;) delimiters, strips UTF-8 BOM headers added by Microsoft Excel, supports quoted multi-word notes containing commas, and processes up to 500 rows in timeout-safe batches of 10.
Jira Administrators see a built-in Erase Customer Data (GDPR) action inside edit mode on any ticket. Confirming immediately deletes the stored profile from Atlassian Forge Storage with no external backups left behind.