With 3.13.0 we've introduced an additional level to the work hierarchy named Portfolio Epics. This is a new entity type above an Epic in a Project.
How Portfolio Epics are used
It’s supposed to be used for portfolio-level planning and would be split into Epics and Features.
Portfolio Epics are very similar to Epics. You can assign several Teams, customize States and Fields, create Metrics, etc.
Portfolio Epics can be related to a single Release and Project. Portfolio Epics can contain Epics and Features related to multiple Projects, Releases, Team Iterations.
History for Portfolio Epics is available since Targetprocess version 3.13.1
To enable Portfolio Epics, an Administrator would go to the Settings of the required process and find a new option in practices list.
Portfolio Epic always belongs to a single Project. It is listed in the Project field in Info panel.
Portfolio Epic may have multiple nested Features and Epics. They are listed on Features and Epics tab correspondingly.
User Stories and Bugs cannot belong to Portfolio Epics directly. You have to assign User Stories and Bugs to intermediate Features that belong to a Portfolio Epic.
Effort and Progress Calculation
Total Effort of a Portfolio Epic having at least one Feature or Epic is always equal to total Effort of its Features and Epics.
Total time spent of a Portfolio Epic is always equal to the total time spent on its Features and Epics. It is not possible to submit Time record to a Portfolio Epic directly.
- How Effort is calculated for high-level scopes of work
- Measuring progress of high-level planning entities
Portfolio Epic details view is quite familiar. It has usual properties and contains a list of related Features and Epics as well as Portfolio Epic progress tracking information. So now you can track progress on a higher level:
Portfolio Epic is quite similar to Epic entity and you can define terminology for Portfolio Epic, create custom fields, set permissions and customize its workflow:
You can export Portfolio Epics, print them and access them via REST API, create Roadmaps with Portfolio Epics, etc.
Advanced Filters by parent Portfolio Epics
Advanced Filter for direct parent Portfolio Epic for Features or Epics:
?PortfolioEpic is "PE1"
Parent Portfolio Epic for Features
You may refer to direct Portfolio Epic of a Feature, or to Portfolio Epic of an Epic of the Feature:
?PortfolioEpic is "PE1" ?Epic.PortfolioEpic is "PE1"
Parent Portfolio Epic for User Stories
You may refer to direct Portfolio Epic of a parent Feature, or to Portfolio Epic of an Epic of the parent Feature:
?Feature.PortfolioEpic is "PE1" ?Feature.Epic.PortfolioEpic is "PE1"