Please add this.
Here’s the specific scenario. I have a project that is shared by multiple engineering teams. There is a “due date” field for the project in the portfolio, but that “due date” does not matter since we need to communicate the individual due dates (tracked as milestones in a project) in another portfolio.
Needed as well!
This would be great to have (I know this is an older entry, but still). We manage our editorial calendar as a project with tasks, and that works well, but portfolios work by department for reporting purposes, so the editorial work tends to not get fed into the overall work we do for those departments.
I added a vote here as well.
Portfolios have a lot of potential but like other commenters I too have struggled with do I really need a “whole project” for this relatively minor initiative and often fallback to using Tasks as Psudeo Projects in a project I name “Project Portfolio.”
While we hope and wait, I’ll take a look at the workaround/kludge of treating these as milestones in a project called Minor Updates or something similar.