Expand All" Option Is Not Available for Subprojects in Tasks / Gantt View

Products

• Clarity PPM On Premise
• Clarity FedRAMP
• Clarity PPM SaaS

Issue/Introduction

When navigating to the Tasks tab (Gantt/Timeline view) of a master project, right-clicking a regular summary task displays the Expand All option in the context menu. However, when right-clicking a row corresponding to an added subproject, the Expand All option is missing.  

Environment

Clarity All Supported Version 

Cause

A subproject entry within a master project's Tasks/Gantt view functions as a proxy link pointing to an independent project record. It does not physically embed or store the child project's task structure inside the master project's local hierarchy.  

Because the subproject's task structure is owned and loaded from the subproject itself, actions that require recursively loading, linking, or duplicating child tasks are restricted from the master project's context menu:  

• Expand All: Withheld to prevent recursive loading of an external project's task hierarchy within the master project view.
• Copy with Children: Withheld to prevent duplicating tasks from an external project scope into the master project.
• Add External Dependency: Cross-project dependency rules do not apply directly through a subproject proxy node.

Actions that manage only the link itself (such as Open Details, Collapse All, Insert Sibling, Insert Child, and Delete) remain available.  

 

Resolution

This behavior is by design

To expand and manage the full task hierarchy of a subproject, open the subproject directly:  

• In the master project's Tasks tab, locate the subproject row.
• Double-click the subproject row, or right-click and select Open Details.
• Once the subproject opens in its own view, navigate to its Tasks/Gantt view.
• Right-click any summary task and select Expand All to view the entire task hierarchy.

 

Additional Information

Note: This design standard applies across Clarity's Work Breakdown Structure (WBS) management. Structural task operations—including Indent, Outdent, Move, and Baseline Updates—are similarly restricted on subproject proxy nodes because task ownership resides exclusively within the subproject itself.