OrgPulse for Jira Service Management
Customer and organization directory for Jira Service Management, with Excel and CSV export and a customer context panel for agents. By PuzariCloud. Privacy policy.
OrgPulse page: customers and organizations
- Open a Jira Service Management project as an agent.
- In the project sidebar, open Apps > OrgPulse. The page opens with the heading OrgPulse: Customers & Organizations.
- OrgPulse reads the project's organizations, their members and the project's customers live from Jira Service Management with your permissions.
Three views:
- Organizations: every organization added to the project, with its member count, its number of requests and open requests (Jira's approximate counts for
Organizations = "name" in this project). Members shows the organization's customers; Requests opens the matching issue search.
- Customers: every customer of the project and every member of its organizations, with email, organizations, the date of their last request and how many of the latest 2,000 requests they reported. Requests opens their requests in issue search.
- No organization: customers who don't belong to any of the project's organizations, so you can tidy them up.
Type in the search box to filter by name, email or organization (case and accent insensitive). Click a column header to sort.
Export
- Export CSV downloads the rows of the current view, with your search and organization filter applied. The file is UTF-8 with a BOM so Excel opens accents correctly, and cells that start with
=, +, - or @ are protected against formula injection.
- Export Excel downloads one workbook with four sheets: Organizations, Customers, No organization, and Memberships (one row per organization and customer pair). Header rows are bold, frozen and filterable; counts are real numbers.
Files are generated in your browser. Nothing is uploaded or kept by the app.
Customer context panel
On a request in a service project, agents can open Customer context from the issue's app context area. It shows:
- the reporter's name, email (if their profile shows it) and local time,
- the reporter's other open requests in the project, their requests in the last 90 days, and open requests from their organizations, each one click away from the full issue search,
- the organizations they belong to, with open request counts,
- their five newest other open requests.
Permissions and limits
- Only agents of a service project can list its customers and organizations. Everything is read with the signed-in agent's own permissions.
- Email addresses hidden by a person's Atlassian profile visibility settings stay blank, so exports may contain names only for those customers.
- The customer list uses Jira Service Management's
/servicedesk/{id}/customer endpoint, which Atlassian marks as experimental. If it is unavailable, OrgPulse shows organization members only and says so.
- Up to 1,000 organizations and 10,000 customers per project are loaded. Last request dates come from the latest 2,000 requests in the project.
- Request counts are Jira's approximate counts and may lag a few seconds behind very recent changes.
Moving from a Connect app
If you used a Connect app such as Customer Tools for JSM or Organizations Automation to see customer and organization details or to export them, OrgPulse covers the read and export side on Forge:
- Install OrgPulse from the Atlassian Marketplace. Nothing needs to be migrated, because OrgPulse keeps no data of its own: it reads organizations and customers from Jira Service Management each time.
- Check the OrgPulse page (project sidebar, Apps > OrgPulse) and the Customer context panel in a service project.
- Uninstall the Connect app when your team is happy. OrgPulse doesn't create or change organizations; keep using Jira Service Management's own settings or automation rules for that.
Support
Email support@puzaricloud.in. We reply within one business day.