-
Suggestion
-
Resolution: Fixed
-
3
-
19
-
Issue Summary
The "Macro usage" page doesn't show correct numbers due to user permissions who access the page.
Activating an Admin Key section also doesn't help to get the inherited required restrictions, which would be useful as a workaround if it did.
Steps to Reproduce
- Create a restricted page.
- Insert a macro to the restricted page.
- Publish the page.
- Navigate to Settings -> Macro Usage (with another user)
- URL:
https://<sitename>.atlassian.net/wiki/admin/pluginusage.actionhttps://<sitename>.atlassian.net/wiki/admin/macro-usage
- URL:
Expected Results
The correct number of macro usage.
Actual Results
The number is less than the actual number.
Workaround
N/A
- is duplicated by
-
CONFCLOUD-73272 "Macro usage" page to include all macros
-
- Gathering Impact
-
- is related to
-
CONFCLOUD-82249 Using Admin key does not show a complete and accurate view of the Macro Usage page
-
- Gathering Impact
-
-
CONFCLOUD-82006 Provide builtin option for identifying macro usage including restricted pages.
- Gathering Interest
- relates to
-
AI-555 Cannot do site-wide search for macros used on pages
- Gathering Interest
-
ECO-470 Usage statistics for third party apps
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
[CONFCLOUD-73281] The "Macro usage" page may not show exact numbers due to user permissions in the pages
Link | New: This issue is related to CONFCLOUD-82006 [ CONFCLOUD-82006 ] |
Link | New: This issue is related to CONFCLOUD-82249 [ CONFCLOUD-82249 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Assignee | New: Ashleigh Christopher [ c833666bd0cd ] |
Description |
Original:
h3. Issue Summary
The "Macro usage" page doesn't show correct numbers due to user permissions who access the page. Activating an *Admin Key* section also doesn't help to get the inherited required restrictions, as a workaround. h3. Steps to Reproduce # Create a restricted page. # Insert a macro to the restricted page. # Publish the page. # Navigate to *Settings* -> *Macro Usage* (with another user) ** URL: -https://<sitename>.atlassian.net/wiki/admin/pluginusage.action- https://<sitename>.atlassian.net/wiki/admin/macro-usage h3. Expected Results The correct number of macro usage. h3. Actual Results The number is less than the actual number. h3. Workaround N/A |
New:
h3. Issue Summary
The "Macro usage" page doesn't show correct numbers due to user permissions who access the page. Activating an [*Admin Key*|https://support.atlassian.com/confluence-cloud/docs/bypass-access-restrictions-on-a-page-with-admin-key/] section also doesn't help to get the inherited required restrictions, which would be useful as a workaround if it did. h3. Steps to Reproduce # Create a restricted page. # Insert a macro to the restricted page. # Publish the page. # Navigate to *Settings* -> *Macro Usage* (with another user) ** URL: -https://<sitename>.atlassian.net/wiki/admin/pluginusage.action- https://<sitename>.atlassian.net/wiki/admin/macro-usage h3. Expected Results The correct number of macro usage. h3. Actual Results The number is less than the actual number. h3. Workaround N/A |
Description |
Original:
h3. Issue Summary
The "Macro usage" page doesn't show correct numbers due to user permissions who access the page. h3. Steps to Reproduce # Create a restricted page. # Insert a macro to the restricted page. # Publish the page. # Navigate to *Settings* -> *Macro Usage* (with another user) ** URL: -https://<sitename>.atlassian.net/wiki/admin/pluginusage.action- https://<sitename>.atlassian.net/wiki/admin/macro-usage h3. Expected Results The correct number of macro usage. h3. Actual Results The number is less than the actual number. h3. Workaround N/A |
New:
h3. Issue Summary
The "Macro usage" page doesn't show correct numbers due to user permissions who access the page. Activating an *Admin Key* section also doesn't help to get the inherited required restrictions, as a workaround. h3. Steps to Reproduce # Create a restricted page. # Insert a macro to the restricted page. # Publish the page. # Navigate to *Settings* -> *Macro Usage* (with another user) ** URL: -https://<sitename>.atlassian.net/wiki/admin/pluginusage.action- https://<sitename>.atlassian.net/wiki/admin/macro-usage h3. Expected Results The correct number of macro usage. h3. Actual Results The number is less than the actual number. h3. Workaround N/A |
Description |
Original:
h3. Issue Summary
The "Macro usage" page doesn't show correct numbers due to user permissions who access the page. h3. Steps to Reproduce # Create a restricted page. # Insert a macro to the restricted page. # Publish the page. # Navigate to *Settings* -> *Macro Usage* (with another user) ** URL: https://<sitename>.atlassian.net/wiki/admin/pluginusage.action h3. Expected Results The correct number of macro usage. h3. Actual Results The number is less than the actual number. h3. Workaround N/A |
New:
h3. Issue Summary
The "Macro usage" page doesn't show correct numbers due to user permissions who access the page. h3. Steps to Reproduce # Create a restricted page. # Insert a macro to the restricted page. # Publish the page. # Navigate to *Settings* -> *Macro Usage* (with another user) ** URL: -https://<sitename>.atlassian.net/wiki/admin/pluginusage.action- https://<sitename>.atlassian.net/wiki/admin/macro-usage h3. Expected Results The correct number of macro usage. h3. Actual Results The number is less than the actual number. h3. Workaround N/A |
Remote Link | New: This issue links to "Page (Confluence)" [ 1026701 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 1026699 ] |
Pinned by
Edson B [Atlassian Support]
Hi everyone,
This is Ashleigh from the Confluence team. Thank you for bringing this issue to our attention.
The behavior of the Macro Usage page intentionally works in this way for security reasons. Under normal circumstances, users including admins should not have any access or insight into restricted content.
To set the right expectations, we are closing this bug as 'Fixed', as we do not have any plans to change the behavior of this feature, but we have added copy to the page to indicate the count may vary based on permissions.
Thank you again for providing valuable feedback to our team! I will be marking it closed for now.
Ashleigh