Feature Request – Application-Level Hierarchy and Onboarding Enhancement

Problem Statement

Our current implementation presents a structural limitation in how we organize and manage projects within your platform. Specifically, we have multiple teams linked to individual projects, which complicates our ability to associate projects with their parent application. This creates friction in our workflow and limits our ability to maintain a clear hierarchical relationship between our applications and their constituent projects.

Solution Brainstorm

Proposed Solution:
We would like to request the introduction of a mandatory "Application Name" field during the onboarding process. This enhancement would establish a three-tier organizational hierarchy as follows:

• Application (top level – proposed new tier)
• Projects (mid-level – existing)
• Teams (base level – existing)

This structure would enable us to:

• Clearly associate multiple projects with their parent application
• Streamline project discovery and management
• Maintain consistent naming and organizational conventions
• Improve cross-team collaboration and visibility

Product Area

Projects - Project Details

No files, tests, or entry points are named. Start by reviewing the Projects - Project Details area and the onboarding flow to locate existing project and team relationships. Done would require an agreed implementation of the mandatory Application Name and the application–project–team hierarchy, but the issue does not define acceptance tests.