What is the relationship between portfolios and fields?

[ka_nishiyama]

I can add fields to portfolios.

What I’d like to know is, can I assume that a field added via “Portfolios > Workflow > Fields > Add” belongs only to this portfolio?

For example, if there is a field with the same name as a field created in another portfolio, can I assume that it is a different field?

Related Help
https://help.asana.com/s/article/portfolios-faq

[Phil_Seeman]

It works the same as fields at the project/task level; that is, if you add it via “Portfolios > Workflow > Fields > Add” and you do not check the “Add to [org name]'s field library” checkbox, then it will belong only to that portfolio. If you do check that box, then it’s eligible to be added to other portfolios at some future point.

[ka_nishiyama]

Hi @Phil_Seeman
Thank you for your explanation.

I tested it myself.

As a result, I came to this understanding:

Suppose you have set local and global fields in separate portfolios A and B.

• Individual local fields can have different values, even if they have the same field name.
• Global fields are shared between portfolios.

[Phil_Seeman]

@ka_nishiyama

• Individual local fields can have different values, even if they have the same field name.
• Global fields are shared between portfolios.

Correct! Again, this is the identical behavior as for custom fields in tasks/projects.

[Jan-Rienk]

@ka_nishiyama adding to @Phil_Seeman ’s accurate explanation: The same field can be available for in projects AND portfolios if added to the library, allowing to have tasks converted to projects carry their custom field values with them.

This is great for project pipelines when you go from form to task to project.