If I’m importing a project via a csv, can I point to a organization custom field that already exists?
Problem is that when importing from a CSV all custom fields are local and as far as I understand created at the point of creation of a project.
So when we create a project via CSV and then add another project to some task (so that the task is in both projects), the fields from the original project don’t show up on that other project. I couldn’t find a way to add it, if it wasn’t an organization custom field.
Can we point to (via name or gid or any other way) to a organization custom field, that has the same values as the local field (plus some additional options) at the point of importing the CSV? That would make it an option to add it to that other project and show it there.
We also don’t want to just create another custom field and have two custom fields with the same/similar name, as that can lead to confusion for the users.
And you’ll find many other answers about importing here: Asana Help Center
Regarding your custom fields across projects questions, the above may be enough info for you, or also read about organization-wide custom fields elsewhere in the Asana Help Center.
Maybe an additional question regarding importing custom fields. Is there a way to limit who can create organization custom fields, so that people dont flood the organization custom field library with very similar Custom fields? Because if we import CSV and local custom fields are created, to prevent just anyone to make them organization custom fields?
Members (those with your org’s domain in the login email address) will have this ability (on paid plans), but Guests (those not with your org’s domain in their login email address) will not.
I don’t think you can prevent this except by removing from project members the Project Admin permission, though for new projects, if they can create a project, then they’ll get that permission.
Somewhat related, but not a solution for you, I don’t believe, is: