Contributor cannot access completed parent work item from sub-work item

Summary

A user with Contributor access inherited through a Teamspace cannot reliably access the completed parent work item from an open sub-work item.

The parent-child relationship is still present in the API, but the web UI does not expose usable parent context/breadcrumb to the Contributor when the parent is Done and the Contributor is not assigned to it.

Environment

• Plane: self-hosted Commercial
• Version: v2.6.3
• Project: private
• User access: Contributor, inherited through a Teamspace
• guest_view_all_features: disabled, but the affected user is a Contributor, not a Guest

Steps to reproduce

1. Create a parent work item in a private project.
2. Create a sub-work item under that parent.
3. Give another user Contributor access to the project through a linked Teamspace.
4. Assign the Contributor only to the sub-work item, not to the parent.
5. Mark the parent work item as Done while leaving the sub-work item open.
6. Log in as the Contributor and open the sub-work item.
7. Try to view the parent request through the parent breadcrumb/context.

Actual behavior

The Contributor cannot see usable information from the parent work item through the sub-work item. The parent breadcrumb/context is missing or does not work, so the assignee cannot read the original request kept in the parent.

The relationship itself has not been removed. A public API request for the child with expand=parent still returns the parent ID, sequence ID, and project ID.

Expected behavior

A Contributor should be able to view all work items in a project, including work items that:

• are Done;
• are not assigned to that Contributor;
• were created by another project member.

Opening a sub-work item should show a usable parent breadcrumb/link and allow the Contributor to open the parent work item.

This appears consistent with the documented Contributor permissions, which grant access to view project work items.

Questions

1. Is this behavior expected for Contributor access inherited through a Teamspace?
2. Is there a project or workspace setting required to make completed parent work items visible to Contributors?
3. Is this a known issue in v2.6.3?
4. Has this behavior been fixed in Plane v3.0.0 or a later release?
5. What is the recommended workflow if a sub-work-item assignee must read the complete request stored in its parent without also being assigned to the parent?

We can provide private instance/task identifiers to Plane support if needed, but have omitted them from this public report.

Reproduce the v2.6.3 scenario with a Contributor inherited through a Teamspace, a completed parent, and an open child. Start by comparing the child’s web UI parent breadcrumb/context with the API response from expand=parent; done means the Contributor can open the completed, unassigned parent from the sub-work item.