Custom page statuses not appearing in Confluence Automation trigger/action despite single space scope

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      In Confluence Automation, when configuring a trigger or action related to "Page Status" (e.g., "Page status changed" trigger or "Change page status" action), custom statuses are not populated in the dropdown menu. This occurs even when the automation rule's scope is correctly set and saved to a single specific space, which according to documentation should surface both suggested and custom statuses.

      Steps to Reproduce

      1. Create a new automation rule in Confluence.
      2. Set the rule's scope to a specific space (not Global) and save the flow details.
      3. Add a trigger "Page status changed" or an action "Change page status".
      4. Attempt to select a status from the dropdown menu.

      Expected Results

      Both "Suggested" and "Custom" statuses defined in the selected space should be visible and selectable.

      Actual Results

      Custom statuses do not appear in the list, only suggested statuses appear.

      Workaround

      It is possible to use custom statuses if they are manually registered as "Suggested statuses" at the space level.

      1. Navigate to Space Settings > General > Avatars and Status.
      2. Add the desired custom status name to the "Suggest statuses" list and save.
      3. Return to the Automation builder and refresh the page; the status will now appear in the dropdown.

      Note: This requires Space Admin permissions and manual maintenance of the suggested status list, which is not ideal for dynamic user-created statuses.

              Assignee:
              Unassigned
              Reporter:
              Unassigned
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: