Teams often need a list of who can raise requests in a Jira Service Management (JSM) project: each Customer, the Organizations they belong to, and their email addresses. Jira has several ways to get part of that list. This guide explains what each one returns, so you can choose the right one before installing anything.
| You need | Use |
|---|---|
| All portal-only customers on your site, as a CSV | Atlassian’s built-in Export customers in the admin console (see section 02). No app needed. |
| Requests with their Organization shown for each one | The issue search (JQL) with the Organizations column, exported to CSV. This lists requests, not a membership list. |
| Organizations and their members for one project, and you are comfortable running a script | Atlassian’s sample Python script, or the Service Management REST API directly (section 04). |
| The Customers and Organization memberships of one project as a CSV, with no script or API token | Customer & Organization Export for JSM (section 05). |
Atlassian documents an Export customers action for portal-only customers. In the admin console, open your organization, go to Products, select your site, then Jira Service Management → Portal customers → Export customers. When the file is ready, a download link appears in the confirmation message. See Atlassian’s article Export portal only customers list, which also covers the older User Management path.
Two things to keep in mind. This is an administrator action in the Atlassian admin console, and it lists portal-only customers for the site; Atlassian’s article does not describe filtering by project or showing Organization membership.
Atlassian’s article Get a list of customer organizations and their users in a Jira service project provides a script for this job, which indicates there is no one-click equivalent in the product. Atlassian tracks the gap in public feature requests, including JSDCLOUD-6160 (export users and organizations per project) and JSDCLOUD-8037 (export organization members per project). As of 27 October 2026 JSDCLOUD-6160 is listed as “Reviewing”. Check the tickets for the current status before relying on this.
The Service Management Cloud REST API has Organization endpoints that return an Organization’s members. Responses are JSON and paginated, so exporting to CSV means writing or adapting a script. Atlassian’s sample script writes organizations_users.csv with Organization ID, Organization Name, User Account ID, User Name and User Email for one service project. It needs Python, an API token and the project’s service desk ID, and Atlassian provides it as-is without support. This is a good option if you already have someone who maintains scripts.
The app is a small page inside Jira for exactly one job: pick a JSM project, click Export CSV, and download that project’s Customers and Organizations. It runs in your browser with your own Jira permissions, so there is no API token to create and no script to maintain.
What it does not do. It exports; it does not import or edit Customers or Organizations, and it does not filter or schedule exports. If you only need the site-wide list of portal-only customers, Atlassian’s built-in export is enough.
Step-by-step details and troubleshooting are in the documentation.