Just been testing the beta feature and it works well with what it can do. For now though it doesn't have the granularity or overall control by me as an admin and quality manager to enforce company policies on approvals.
For that to work, we would need the points I described in my first post, but at least more extensive dynamic controls via automations (set approvers dynamically by smart values and adding approvers to already running approvals) so we could work around the other limitations by outsourcing the actual "approver management" and approval stages to Jira.
Edit: One big limitation that I just found, is that I can't set a page to be approved by myself. Not even by automations. That means I could never set up a flow to be triggered by other users that requires my approval. Since we still don't have a Confluence Automation User like in Jira, this limitation should not be there in my opinion.
26 comments