Automation space dropdown returns too few spaces for high‑permission users with many personal spaces

XMLWordPrintable

    • 1
    • Severity 3 - Minor
    • 3

      Issue Summary

      For such a high‑permission user, the Automation rule builder’s Space dropdown only shows one regular (non‑personal) space as a selectable option.
      This happens because the underlying SpaceSelectorQuery is limited to 50 results; those 50 entries are mostly personal spaces, which the UI then filters out, leaving almost no regular spaces visible.

      Preconditions

      • Confluence Cloud site with:
        • A large number of personal spaces (space keys starting with ~).
      • A high‑permission user who:
        • Has view permission on many personal spaces owned by other users (not just their own personal space).
        • Also has view permission on multiple regular (global) spaces.

      Note: This is a relatively rare setup; in many sites, even admins do not typically have effective visibility into a large number of other users’ personal spaces. This condition is important to reproduce the issue.

      Steps to Reproduce

      1. Log in as the high‑permission user described in the Preconditions (can view many other users’ personal spaces and multiple regular spaces).
      2. Open any space → go to Automation and create or edit a space‑level rule.
      3. Add an action that has a Space picker, for example:
        • “Publish new page”
        • “Copy page”
        • “Move page”
      4. Click the Space dropdown without typing any search text.

      Expected Results

      • The Space dropdown lists multiple regular (non‑personal) spaces that the user can select (similar to the macro configuration space picker for the same user).

      Actual Results

      • The dropdown shows:
        • A few fixed options (e.g. “Same as trigger”, “Current space”, “All spaces”, etc.), and
        • Only one regular space as an actual selectable space.
      • When a narrow‑permission user (who cannot see many personal spaces) performs the same steps on the same site, they see multiple regular spaces in this dropdown.

      Technical Notes (HAR / GraphQL)

      • HAR shows a request to:
        • POST https://<company_name>.atlassian.net/gateway/api/graphql
      • Query: SpaceSelectorQuery
      • Variables include, for example:
        • cql: "type = 'space'"
        • limit: 50
      • Response:
        • Exactly 50 space entries are returned.
        • The majority of these entries have keys starting with ~ (personal spaces).
        • Only a very small number (e.g. 1–2) are regular (non‑personal) spaces.
      • Automation UI behavior:
        • The Automation space dropdown filters out personal spaces on the client side.
        • Because the 50 results are dominated by personal spaces, almost all returned entries are removed by this filter.
        • This leaves only a single regular space visible in the dropdown for the affected high‑permission user.

      Workaround

      • Available workaround:
        • Configure Automation rules using a user with narrower space permissions, such that:
          • They cannot see many other users’ personal spaces,
          • The first 50 results returned by SpaceSelectorQuery are mostly regular spaces,
          • The Space dropdown then shows multiple regular spaces as expected.
      • Limitation:
        • There is currently no known workaround that allows the affected high‑permission user (who can see many personal spaces) to see all intended target spaces directly in the Automation Space dropdown.

              Assignee:
              Unassigned
              Reporter:
              Kyungmin Kim
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: