Issue Summary

At the moment, there is no supported way via Atlassian Cloud Organization/Admin APIs to retrieve a complete list of all users who have or had Jira Software access, including inactive / deactivated / ex‑Jira users.

Customers can only:

• Use Admin V2 “users in directories” APIs to get all managed accounts + org status, but no product‑level access information.

• Use Jira REST APIs or groups (e.g. jira-software-users) to get current Jira Software users, but not users who previously had Jira Software access and have since been removed.

• Use the Export users feature in the UI to get a CSV with product access and status, which is not suitable for automated, API‑driven integrations.

This creates a gap for customers who need an API‑driven and automated way to know exactly which users are/were licensed for Jira Software for reporting, integration, compliance, and billing purposes.

Expected Results

Provide a supported, stable Organization/Admin API (or extend existing endpoints) that can:

1. Return a bulk list of managed accounts with a reliable, non‑empty per‑product access structure.
2. Allow filtering or post‑processing on the client side to answer questions such as:
   • “Give me all users who have or had access to Jira Software (jira-software), including inactive/deactivated accounts.”
3. Be safe and supported for automation and long‑term integrations (not marked as deprecated).
   This could be achieved, for example, by:

• Adding a populated product_access array to existing Admin endpoints such as:
  • GET /admin/v2/orgs/{orgId}/directories/-/users
  • GET /admin/v1/orgs/{orgId}/users
• Or exposing a new endpoint like:
  • GET /admin/vX/orgs/{orgId}/product-access?productKey=jira-software
    which returns all users (active + inactive) and their relationship to that product.

Actual Results

• Admin V2 directory users: no product access information at all.

• Admin V1 org users: product_access field exists in schema but is empty in practice.

• Per‑user last‑active API does expose product_access but is per‑user only (no bulk), is deprecated and will stop working after June 30, 2026.

• Jira site‑level APIs only expose current Jira Software users, not those who previously had access.

• Customers cannot, via API alone, build a reliable list of all active + inactive / historical Jira Software users.

Workaround

• Non‑API workaround:

• • Use Export users in Atlassian Administration with:

• • • Jira Software groups selected,

• • • All user statuses,

• • • Product access + group membership columns.

• • Limitation: Manual or semi‑manual; not suitable for fully automated, API‑based integrations.