Hive Start free trial
Feature requests › Everything else › Add project-level cascading for project custom field selections

Add project-level cascading for project custom field selections

4 votes0 repliesAsked by Andrew Naisawald

Teams that use nested projects need project custom field selections to stay consistent across a project hierarchy without manually configuring the same selections on every sub-project. Today, this creates duplicate setup work and can lead to inconsistent reporting or filtering across related projects.

Requested behavior:

- Add a project-level or project custom field selection-level option that allows selected project custom field values to cascade from a parent project down through nested sub-projects.

- Cascade should be configurable per project hierarchy, not workspace-wide.

- When enabled, nested sub-projects should inherit the applicable selection from the nearest ancestor project unless the sub-project has an explicit selection of its own.

- Behavior should align with existing action custom field cascade logic where applicable.

Acceptance criteria:

- Cascade applies through all nested sub-project levels, not only direct child projects.

- Sub-projects inherit from the nearest ancestor with cascade enabled.

- Explicit sub-project selections override inherited selections if overrides are supported.

- Updating or removing a cascading parent selection updates inherited behavior for nested sub-projects.

- Projects without cascade enabled keep existing behavior.

- Tests cover enabled/disabled cascade, direct and deeply nested inheritance, override behavior, and parent update/removal behavior.

Read the full discussion in Hive Network

Start a free trial to read every request and its replies in Hive Network. Teams on a paid plan also vote and post.

Start free trial Already use Hive? Sign in

More everything else requests