When an issue is restricted, users outside its security level currently cannot see it at all. The issue is not only hidden in terms of content; it is completely removed from boards, JQL results, parent fields, and roadmaps. This breaks the hierarchy and creates confusion, since child issues appear to have no parent even though one exists.

As a result, roadmaps and plans contain gaps, and large-scale planning items (for example, sagas that include sensitive information) are hard to represent accurately at an organization-wide level.

We would like to propose an alternative behavior: instead of fully hiding restricted issues, show non-authorized users a minimal placeholder containing only the issue key, type, summary, and status. Attempting to open the issue would still block access to any restricted fields. This approach would maintain hierarchy, safeguard sensitive data, and ensure that company-wide roadmaps remain complete and accurate.