Hello!
I’m hoping I can explain this question well… I think I discovered a small work around to bulk add sections, tasks and subtasks from one project to another using the CSV import tool. Only problem is, the columns that are imported come in as custom fields created by me. I would love if there was a way for them to be imported and link to an already created custom field that is saved in our library. That way I can continue to track and pull reports based on the inputted values within that custom field.
At the moment, I am having to import the sections, delete the custom fields that come in and replace with the custom fields saved in our library. I then need to manually select the value for each task even though it was previously pre-filled prior to the import.
Thanks for any advice! 
@AmyPeters,
First, create the destination project and add to it the org-wide custom fields you want, then after that do your import, making sure the columns in the CSV match and the values in the rows match available options (for single/multi-selects).
You can review this section first to make sure you’re covering the bases:
Hope that helps,
Larry
1 Like
Hello Larry,
Thank you for your response!
I have that part figured out but am now coming up to another small hurdle. The subtasks are also linked to custom fields automatically but when the CSV form is imported into the project, it is only linking itself to the custom fields with the tasks and is not inserting the custom-field values to the subtasks. Any idea why that might be?
Amy
@AmyPeters,
I’m glad the shared custom fields part is working.
As to subtasks getting custom field value, I don’t know for sure but I suppose it might be that, for better or worse, Asana only chooses to import custom fields for parent tasks, not for subtasks. It sounds like that’s what you’re running into. Maybe you can do a little test to confirm that?
If the above is true, all I can think of is the workaround to not treat these rows as subtasks and, after import, drag them one-by-one into their appropriate parent tasks to become subtasks then. I’m not positive this will work, and may well be too much manual effort, so…
You could send the files and reference to this thread to support@asana.com and they will be the best source to help you.
That was a great work around idea, Larry. Thank you!
Unfortunately, I get held up with single-selecting each task into the parent task to make it a subtask again. Maybe shaves off a few seconds but nothing ground breaking.
That being said, I’ll get a note off to support to see if they can request an improvement on this process.
Thank you,
Amy
1 Like
This topic was automatically closed after 6 days. New replies are no longer allowed.