Child page does not inherit page restrictions from parent page
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
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.
*Fisheye および Crucible は除く
問題
A child page is supposed to inherit the page restrictions from its parent page, but, for some reason, it does not inherit any restrictions.
診断
Double confirm that the parent page has restrictions applied. Else, create a new page, add some restrictions to the page and create a new child page under it. The child page will inherit those restrictions by default. This will be depicted by an open red padlock icon. Note: Only view restrictions are inherited, Edit permissions are not inherited. See CONFSERVER-5095 - Getting issue details... STATUS
原因
The ancestor table will become out of sync occasionally.
ソリューション
次の URL にアクセスします：
http://yoursite/admin/permissions/pagepermsadmin.action
After rebuilding the ancestor table, you need to flush the "Inherited Content Permissions" cache in Cache Statistics, otherwise, the inherited permissions may not be applied immediately to all pages. You may also need to rebuild the content index so that the restriction will take effect.
スクリーンショット：ページレベル権限
