Content Report Table does not identify correctly labeled pages
Platform Notice: Server, Data Center, and Cloud By Request - This article was written for the Atlassian server and data center platforms but may also be useful for Atlassian Cloud customers. If completing instructions in this article would help you, please contact Atlassian Support and mention it.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Content Report Table such as Meeting Notes blueprint does not identify and list out pages that has been labeled correctly. It will display:
- "No Content Found"
Happened to other macros such as:
- Blog pages
Diagnosis
- Check if there is any permissions applied to the page.
- The permissions should not be empty
Cause
If there are no permissions set in the space. macros like the Content Report Table or Blog Post will not display the content, because the content does not pass permission checks.
Resolution
Permissions need to be applied in space levels as these macros will perform permission checks
- In the affected space, go to Space Tools > Permissions
- Add permissions to this space.
- If this space is suppose to be restricted to certain users, at least add these users in the "individual users"
Related Content