1. Quick Start
- Install Customer Context Card from the Atlassian Marketplace into your Jira Cloud / Jira Service Management site.
- Open any issue with a reporter assigned and click Customer Info in the right-hand issue context sidebar to display the card.
- Click Edit Customer Details to set the customer tier (
VIP,Enterprise,Standard,Trial, orAt Risk) and save your first customer notes. - To customize fields or import existing records, go to Jira Settings → Apps → Customer Context Card Settings (Jira Administrators only).
2. Custom Field Types
Administrators can configure up to 15 customer fields and 15 organization fields, reorder them with Up/Down controls, or remove unused fields. Four native field types are supported:
- Single-line Text (
text): Ideal for Contract IDs, direct phone numbers, account managers, or device serial numbers (up to 250 characters). - Multi-line Notes (
multiline): Longer escalation instructions, timezone rules, or onboarding context (up to 1,500 characters). - Clickable URL (
url): Renders as an instant clickable link to Salesforce, HubSpot, Stripe, Confluence, or your ERP. Bare domains likecrm.acme.com/123are automatically upgraded tohttps://; unsafe schemes such asjavascript:ordata:are rejected. - Dropdown Select (
select): Enforces consistent values such as SLA tiers or billing regions (up to 20 comma-separated options).
3. Automatic JSM Organization Context
Whenever a ticket belongs to a Jira Service Management Organization, Customer Context Card automatically detects the Organization custom field (language-agnostic across English, German, and localized Jira sites) and renders a shared Organization section directly underneath the individual customer details.
Updating an Organization profile on one ticket immediately makes those details visible on every other ticket submitted by colleagues from the same company.
4. Bulk CSV Import (Timeout-Safe)
Admins can onboard up to 500 customer profiles per upload directly from Customer Context Card Settings. The built-in RFC-4180 parser handles:
- Automatic delimiter detection for both comma (
,) and semicolon (;) exports from Microsoft Excel and Google Sheets. - Quoted fields containing embedded commas, escaped quotes (
""), Windows CRLF endings, and UTF-8 BOM prefixes. - Case-insensitive matching on
email,tier, and dropdown options, processed in controlled batches of 10 rows to stay well below Forge timeout limits.
Example CSV Format
The first row must contain an email column matching existing Jira customer emails, plus optional tier and any configured field IDs shown in your Settings page:
email,tier,customer_id,phone,sla_tier,crm_url,notes elena.vance@acmecorp.com,VIP,ACME-8841,+41 44 580 12 90,24/7 Critical (1h),https://crm.example.com/accounts/8841,"VP of Operations, escalate P1 tickets immediately" marcus.weber@acmecorp.com,Enterprise,ACME-8842,+41 44 580 12 95,Priority (4h),https://crm.example.com/accounts/8842,"Handles EU cloud rollout, German & English speaker" claire.dubois@helvetiatech.ch,At Risk,HT-3090,+41 22 518 44 10,Priority (4h),https://crm.example.com/accounts/3090,"Renewal in 30 days, verify every SLA response"
5. Permissions & GDPR / FADP Data Erasure
- Agent Editing Control: By default, support agents can edit customer and organization fields directly from tickets. Uncheck Allow support agents to edit customer and organization fields in Settings to enforce read-only access for agents and restrict modifications strictly to Jira Administrators.
- 1-Click Data Erasure: Jira Administrators see an Erase Customer Data (GDPR) and Erase Organization Data control inside edit mode. Confirming permanently deletes the corresponding key from Atlassian Forge Storage.
6. Minimal Permission Scopes
| Scope | Purpose |
|---|---|
read:jira-work |
Reads the active issue's reporter, linked JSM Organization field, and up to 5 recent tickets by the same reporter via /rest/api/3/search/jql. |
read:jira-user |
Checks Jira Administrator permission (/rest/api/3/mypermissions) and looks up Jira user account IDs by email during admin CSV import (/rest/api/3/user/search). |
storage:app |
Stores field definitions, customer profiles, and shared organization notes inside encrypted tenant-isolated Atlassian Forge Storage. |
7. Support & Feedback
Questions, feature requests, or security review questionnaires? Reach our engineering team anytime at support@cleardesklabs.com. We typically respond within 1 business day.