Allow project custom fields to inherit info from portfolio custom field

English Forum Product Feedback
1

We have several custom fields that are used both at the portfolio and project level (ex. Customer, Brand, Pack Size) as this information is used for filtering, grouping, searching, dashboards, etc. It is cumbersome to keep all task custom fields updated when the information changes, and it would be incredibly helpful to be able to connect project fields to portfolio fields so they populate/update when changed at the portfolio level. Because this takes so much time to manage, it usually only gets changed at the portfolio level, but this makes it more difficult for users to organize their My Tasks view, since the task custom fields in the project aren’t kept up to date.

1 Like
2

@leferg, Don’t forget to click the title to scroll to the top and vote by clicking the Vote button; that’s the quickest and most effective way to express your support for a request.

You could probably work around this by a rule in each project that for each new task added, default the set of custom fields to the project-specific values.

Respectfully, I’d submit that it may be unlikely that Asana implements this feature because of how they see portfolio and project fields as different things, not the same thing.

If you’d accept another implementation, perhaps change this request or add another one that describes the problem you need solved (what you wrote about My Tasks organization) without this particular solution as the requirement.

Thanks,

Larry

3

I’ve been searching the forum this morning to see if anyone else has reported this issue. All my projects share the same custom fields, and I’m trying to set up the Portfolio dashboard that provides a high-level overview using those fields. However, I’m unable to do so. While the charts are helpful, it would be great to have the ability to view the underlying data by clicking on a chart, rather than navigating to each project’s dashboard individually

4

Unfortunately a rule would not be a viable solution, since we would also need the task custom field info to change if it changes at the portfolio level. For example, if a customer decides to launch the product under a different brand after the project has started, we would want that information to trickle down into the task fields so that information is visible everywhere.