This "feature" is completely justified. IT administrators of Confluence in big companies don't care at all of the content of pages. It needs to stay in the hands of spaces users.
When copying a Confluence page which already contains the approval macro, the same approvers will appear in the approval macro in the copied page. Currently neither the page author nor a space administrator can unregister the unwanted approvers from the approvers list. Our users need to contact the IT-support to request the unregistration of approvers by a confluence administrator.
I agree, it does not make sense that only Jira system administrators can unregister approvers. This is a task absolutely related to the handling of content which should be in the hands of space administrators.
Sayed Bares
This "feature" is completely justified. IT administrators of Confluence in big companies don't care at all of the content of pages. It needs to stay in the hands of spaces users.
Attachments Open full size
When copying a Confluence page which already contains the approval macro, the same approvers will appear in the approval macro in the copied page. Currently neither the page author nor a space administrator can unregister the unwanted approvers from the approvers list. Our users need to contact the IT-support to request the unregistration of approvers by a confluence administrator.
Attachments Open full size
I agree, it does not make sense that only Jira system administrators can unregister approvers. This is a task absolutely related to the handling of content which should be in the hands of space administrators.
Attachments Open full size