IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-79247

Confluence Automation fails to update page status when the scope is set to multiple spaces

      Issue Summary

      Confluence Automation fails to update page status when the scope is set to multiple spaces

      Steps to Reproduce

      1. Create a custom status with the same name and color on two separate spaces
      2. Create an automation rule, with the following steps:
        • Branch rule / related entities - CQL=type = page
        • Action - Change page status - Select the custom status created on the first step
      3. On the rule's details, select scope as "Multiple spaces" and list the two spaces you created the custom status on
      4. Save the rule
      5. Run the rule

      Expected Results

      The rule will sweep all pages on each of both spaces and add the custom status to all pages

      Actual Results

      The rule will fail to change the page status from one of the spaces.
      When selecting the status on the action "Change page status", the list will be populated with all statuses from all spaces in scope, comparing their name and color, but not their ID. The custom status will be listed only once from one space.
      When the rule is run, it uses the custom status ID to update the pages. This will work for all pages in one space, but it won't find that status ID for the pages in the other space.

      Error: We can’t run a rule relating to page status on a global scope. Select Rule details and change the Scope field to one or more space.

      Workaround

      Create an automation rule for each space, instead of selecting multiple space scope

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Confluence Cloud'
            1. Confluence Cloud
            2. CONFCLOUD-79247

            Confluence Automation fails to update page status when the scope is set to multiple spaces

                Issue Summary

                Confluence Automation fails to update page status when the scope is set to multiple spaces

                Steps to Reproduce

                1. Create a custom status with the same name and color on two separate spaces
                2. Create an automation rule, with the following steps:
                  • Branch rule / related entities - CQL=type = page
                  • Action - Change page status - Select the custom status created on the first step
                3. On the rule's details, select scope as "Multiple spaces" and list the two spaces you created the custom status on
                4. Save the rule
                5. Run the rule

                Expected Results

                The rule will sweep all pages on each of both spaces and add the custom status to all pages

                Actual Results

                The rule will fail to change the page status from one of the spaces.
                When selecting the status on the action "Change page status", the list will be populated with all statuses from all spaces in scope, comparing their name and color, but not their ID. The custom status will be listed only once from one space.
                When the rule is run, it uses the custom status ID to update the pages. This will work for all pages in one space, but it won't find that status ID for the pages in the other space.

                Error: We can’t run a rule relating to page status on a global scope. Select Rule details and change the Scope field to one or more space.

                Workaround

                Create an automation rule for each space, instead of selecting multiple space scope

                        Unassigned Unassigned
                        eb1fd8d9a341 Luis Pellacani
                        Affected customers:
                        6 This affects my team
                        Watchers:
                        15 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            eb1fd8d9a341 Luis Pellacani
                            Affected customers:
                            6 Vote for this issue
                            Watchers:
                            15 Start watching this issue

                              Created:
                              Updated: