Documentation · v2.1

Customer Context Card — Setup & Admin Guide

Everything you need to install, customize fields, configure permissions, and bulk-import customer profiles in under 5 minutes.

1. Quick Start

  1. Install Customer Context Card from the Atlassian Marketplace into your Jira Cloud / Jira Service Management site.
  2. Open any issue with a reporter assigned and click Customer Info in the right-hand issue context sidebar to display the card.
  3. Click Edit Customer Details to set the customer tier (VIP, Enterprise, Standard, Trial, or At Risk) and save your first customer notes.
  4. To customize fields or import existing records, go to Jira Settings → Apps → Customer Context Card Settings (Jira Administrators only).
Ready out of the box Customer Context Card ships with thoughtfully preconfigured defaults for both Customers (Contract ID, Direct Phone, SLA Level, CRM Link, Internal Notes) and Organizations (Contract Plan, Account Manager, Company Wiki/CRM, Shared Org Notes).

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:

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:

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"
Tip: Updating existing customers Re-importing an email address merges new column values with any existing saved fields for that customer without wiping unrelated fields.

5. Permissions & GDPR / FADP Data Erasure

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.