-
Suggestion
-
Resolution: Fixed
-
None
-
1
-
4
-
Currently, automating the editing of Confluence pages, blogs, or other content requires the use of web requests to interact with the Confluence Cloud REST API. This process can be cumbersome and requires technical knowledge of API endpoints, authentication, and payload structures. To streamline the automation process and make it more accessible, we propose a feature enhancement that allows users to directly edit content through automation rules without needing API interactions.
Benefits:
- Simplifies the automation rule creation process, making it more user-friendly.
- Reduces the complexity and technical barrier for users who want to automate content updates.
- Enhances productivity by allowing more intuitive and straightforward automation configurations.
- Encourages wider adoption of automation features by lowering the entry threshold for non-developers.
Proposed Solution: Introduce new actions within the Confluence automation interface that allow users to select and edit specific content elements (such as text, tables, or sections) directly. These actions should be configurable with parameters to specify the content to be edited and the type of modifications to be made.
- duplicates
-
CONFCLOUD-77883 Automation for Confluence Edit Page Body rule
- Closed
- is related to
-
AUTO-1768 Improve Create Confluence Page action in A4J - templates, add body editor & ability to pass Jira smart values to Confluence page template, e.g. to support "Create Release Notes in Confluence" use case, ability to link Jira fields to Confluence table
- Closed