Every customer and organization, with their request counts.

On the admin page, click Scan all projects to read every service project, one after the other. To scan one project, choose it in the Service project box and click Scan this project. Projects with no finished scan show not scanned yet in that box. On a project's own page there is only Scan this project.

For each project the scan reads the customers, the organizations added to the project and their members, and then the project's requests, once. A progress line shows the project, its place in the scan, the step it's on and how many requests it has read so far. You can leave the page; the scan carries on. On a big site it can take a while.

• If a scan makes no progress for 20 minutes, the page offers Start again. Work already done in that scan is dropped.
• If one project fails, the scan says finished with problems, gives the reason, and moves on to the next project.
• If two people start the same scan at the same moment, one scan runs and the other person is told to wait a moment and refresh the page.

The Customers tab lists everyone added to the project, and everyone in an organization added to the project. The tab shows how many match the filters. Columns:

• Name and Email, looked up from Jira when the page is shown. Not shown means Jira did not give the app that email.
• Customer through: Added to project, the names of the organizations that make them a customer, or both.
• Open and Resolved: the requests they reported.
• Last request: the date of their most recent request, or No requests.

Customers with the most requests come first. The list shows 25 at a time; use Previous and Next to page through.

• Organization: pick one organization to see only its members on the Customers tab and only that organization on the Organizations tab. Clear it to go back to All organizations.
• Only customers and organizations with no requests: tick it to find the customers and organizations that have raised nothing.
• Scan: the last three finished scans of each project are kept. When there is more than one, pick a date and time here to see that scan. When a new scan finishes, the page shows the newest one.

The filters also apply to the export.

• Resolved means the request has a resolution: the Resolution field is set. That is what Jira Service Management uses for closed requests. A request with no resolution is open, even in a done status. The page and the About sheet say how many such requests there are.
• A request counts for its reporter. A request raised on someone's behalf counts for the person shown as the reporter.
• A request counts for each organization it is shared with. If the site has no Organizations field, organization counts are zero and the page says so.
• Requests raised by people who are not customers of the project, such as agents, are counted in the summary note, not in the lists.

The scan reads each request once and asks Jira for six fields only: reporter, Organizations, resolution, resolution date, status category and created date.