-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
Changing the Scope on a Confluence Automation rule that uses the Change Page Status action causes a silent loss of Page Status selection and will allow users to Update the rule with an empty selection.
This happens due to Statuses being Space-specific and, despite having the same title and color, are unique to each Space.
Example:
Status Title | Status Color | Status ID in Space A | Status ID in Space B |
---|---|---|---|
Rough draft | #ffc400 | 708123 | 708234 |
In progress | #2684ff | 708124 | 708345 |
Ready for review | #57d9a3 | 708125 | 708236 |
Verified | #1d7afc | 708126 | 708237 |
Steps to Reproduce
Steps:
- Create a new Automation rule for Space A
- Add a Change Page Status action and select a Page Status
- Turn On the new rule
- Go to Confluence Administration > Automation and find the rule created
- Under 'Rule Details', change the Scope to Space B
- Click Update
Expected Results
Changing the rule's Scope should produce an error in the Change Page Status action, inform the user that a new Page Status is required and preventing the user from Updating the rule without a new Page Status being selected.
Actual Results
The rule is Updated without errors, but further executions will fail due to a Page Status not being selected. Also, the Audit Log does not indicate what caused the error and makes it difficult to troubleshoot.
Clicking the Change Page Status will produce a "We could not find the specified content statuses. Please try again." error and highlight the Page Status box in red.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
CONFCLOUD-79247 Confluence Automation fails to update page status when the scope is set to multiple spaces
-
- Short Term Backlog
-
-
CONFCLOUD-80958 Allow global page status updates via Confluence Automation
- Gathering Interest