Hello customer!

We'd like to suggest a change to support Portfolio Epics to reside in a portfolio area path in Azure DevOps for improved integration with JA.

Currently, the integration requires Portfolio-level work items to exist at the program area path in Azure DevOps for Portfolio Epic integration. However, this setup is challenging to maintain and manage at scale given that these items are located at the Portfolio level.

The current arrangement creates behaviors that are counterproductive to the scaled agile practices that Azure DevOps is designed to support. Consequently, this hinders the smooth integration of Portfolio Epics with JA. Addressing this issue will not only streamline processes but also enhance the overall user experience and effectiveness of the integration.