In the Adobe Workfront object hierarchy, a Portfolio is a high-level container designed to group and manage a collection of related projects and programs. This structure is fundamental for strategic planning and oversight. Therefore, a Portfolio acts as a parent object, with projects and programs being its direct child objects. While a project is a parent to tasks, the portfolio's primary and defining function is to serve as a parent container for other major work objects like projects.

A. Issue: An Issue represents an unplanned work item and is typically a child object linked to a project or a task. It does not function as a parent object.

B. Project: While a project is a parent object to tasks, it is also a child object within a portfolio or program. The portfolio is a higher-level strategic container.

1. Adobe Experience League - Get started with Adobe Workfront portfolios: This document states

"A portfolio is a collection of projects

and optionally

programs." This explicitly defines the parent-child relationship where the Portfolio is the parent. (See the "Overview of Adobe Workfront portfolios" section).

2. Adobe Experience League - Adobe Workfront object hierarchy: This guide visually and textually represents the object hierarchy

placing Portfolios at a higher level than Projects. It clarifies that Portfolios contain Programs and Projects

which in turn contain Tasks. (See the "Object hierarchy diagram" and "Object relationships" sections).

3. Adobe Experience League - Projects overview: This source describes a project as a collection of tasks. It notes

"A project is a planned set of interrelated tasks..." This confirms a project can be a parent

but the documentation on portfolios establishes the Portfolio as the higher-level parent container for projects themselves. (See the introductory paragraph).