CSV Import for Project Tasks

2 posts were split to a new topic: Issue with CSV importer

Apologies for the delay in responding to you @Karol_Dixon_de_la_O. Marie here, stepping in for @Natalia.

So from what I understand, when importing your CSV and trying to remap “Collaborator” and “Tags”, you can’t find these options in the dropdown menu. Is there any chance you’ve already used these field in another column?

Also, in order for these two fields to appear, make sure that you follow advice listed in this article: CSV Importer • Asana ( Assignee: assign one owner to each task by adding email addresses of valid Asana users from your workspace or organization. Tasks created in Asana can only be assigned to one teammate).

In order to continue investigating this, I would need to access your CSV file, because so far I wasn’t able to reproduce with any of my test CSV. Would you mind sending this CSV by DM? (YOU can send me DM by clicking on my name at the top of this post and select “Message” - please don’t share the file publicly :slight_smile: )

Could you also send a screenshot of what your seeing in Asana when trying to remap these two fields?

Again, so sorry for the trouble, and thank you so much for your patience and cooperation!

Take a look at your new CSV importer – the fields for Collaborator, Tags and a couple others we don’t use are no longer in the drop down options:


Instead, they are mapped as custom fields with drop-down selections which is NOT the same as mapping directly to the Asana designated “Collaborator” field and/or “Tags”

To answer your questions:

  1. No, I have not used those fields in another column (My previous screen shot of the CSV file shows all of the columns we are using)
  2. Yes, we follow the rules in that only one owner is assigned to each task. BUT note, the prior CSV importer allowed that owner to be a non-Asana user, there used to be a checkbox to allow us to have Asana email a new Asana user with tasks assigned to them. This functionality has gone away.
  3. I am guessing you are not able to reproduce if you do not yet have the new CSV importer loaded on your account (the rollout messaging indicated that not everyone would receive it at the same time)

In addition to jumping on this forum to find solutions, I had also clicked on the feedback form for the process and submitted my inquiries there as well. Separately I received the following information from Asana:
Regarding knowing when the import has completed:
We have an update for this that you should see within a week. The message in the bottom left will indicate how many tasks we are importing, and when there import is completed, the message will indicate this.

Regarding the collaborator column
Assuming this column contains email addresses of users you want to add as collaborators, we also have an update coming that will enable you to map to this field. This should also be available within a week.

I am still working out with them what happened to the ability to map to the other fields like “Tags”

@Karol_Dixon_de_la_O, I just spoke with the PM in charge of the new CSV importer (Tony) who confirmed he is already in touch with you to work on this bug, so to avoid any confusion, and in order to resolve this issue as efficiently as possible, I’ll let you work on this together and close this thread in the Forum for now! Thanks again for your cooperation and willingness to help us resolve this issue, we really appreciate it.

Have a great day!

Could you update us on if this has been fixed? Moving the conversation to a private thread doesn’t let us know the outcome. Thanks!

2 Likes

Hi Todd,

Great point and here’s a summary to the questions asked above:

We have some additional functionality rolling out over the next 7 days that addresses some of the questions asked here:

  • Dependents will be enabled as a mappable field
  • Collaborators will be enabled as a mappable field (and now supports multiple collaborators)
  • The import status message in the bottom left will update when the import has completed

Other answers

  • Importing to organizational custom fields can be done but requires the organizational custom field to be added to the project first. We’ll be adding clearer instructions in the guide for this. The reason behind this is that project-local custom fields are less confusing for newer users.
  • The invite functionality is no longer in the CSV importer due to some confusion it was causing (the importer isn’t clear on where the invited users were getting invited to, what they’ll have access to, what their experience will be). We recommend using our project invite screen which we’ll continue to improve. Invited users can then be utilized in the importer for assignee/collaborator.
5 Likes

Hi Tony,

Will Tags be enabled to be a mappable field?

Thank you.

2 Likes

Good morning Tony!

Can you elaborate on what you mean by:

While we will usually have organizational custom fields set to a project prior to importing, it was always nice to be able to search the library for any Custom Fields that columns needed to be mapped to. I’m not a big fan of new Custom Fields of the same name (but limited field options) being created for the project otherwise.

Also, since the new importer doesn’t support the invite functionality what happens when a new user is set as an assignee or collaborator? Does it throw an error or what?

Thanks!!!

Hi Jerod,

Thanks for your follow up questions. Organizational custom fields have the benefit of maintaining consistent types and field options (for dropdowns) across your projects and teams, but becomes problematic when a user intends to use a field of the same name with different possible values or a different type. The most common example we often see of this is “Status”, where different projects of different types may use different statuses. When importing, this often means the column ends up being incompatible with the existing organizational custom field. Changing any of the dropdown values will also impact across all projects using that field (which could be desired or undesired).
When consistency is desired between projects → templates can be helpful in ensuring projects are setup the same way with the same organizational custom fields. We’ll definitely take this feedback of being able to search for organizational custom fields within the custom fields as potential future add.

The import will make a best effort - when an email that does not belong to any user in Asana is used, the task will still be successfully created but won’t have the user applied.

2 Likes

Thanks for the clarification, @TonyC. That makes a lot of sense. When a user is intending to import to an existing organizational custom field it does require an extra step however (- having to add organizational custom field to the project prior to importing).

The ability to browse the library to a organizational field would be really helpful. Furthermore, have you thought about offering any indicators for the users to tell when a custom field is indeed leveraging a organizational custom field rather than creating a new? This may help them ensure everything is being mapped correctly before proceeding.

Good morning, @TonyC!

Are we on track with these updates?

Anything anything else to expect?

Hi @LEGGO, dependents, collaborators and the import completion message should now all be available!

1 Like

Thank you for the new import completion messaging and the ability to map collaborators.

I don’t remember quite what you said about mapping the tags field to the pre-existing one. Will that one be possible in the new import process? We use 2 tags across all projects for specific tasks. It was part of the import process to map them to the asana tab field. Now they are showing up as organizational fields – unfortunately that means, after the import, i need to manually add tags to those tasks and remove the auto-generated organizational fields for tags. This is because we have a body of projects already in Asana that have these tags on them and to move them all to an organizational field would be an effort and we would loose the asana functionality tied to the tags field (i.e. making the tag a favorite and being able to pull a cross-project list of all the tagged tasks)

1 Like

Hi @TonyC, just read through this whole thread and am unable to find a definitive answer to the question about importing tags. It doesn’t seem like it’s currently an option, unless I’m totally missing something somewhere here and while using the import function.

If it actually isn’t an option, are there plans to eventually bring this into play? (That is – mapping tags to the Asana tag fields as opposed to text in the description.) In my current situation, bulk importing tags would be one of the most time-saving uses of importing a CSV. Would love to know what the status is! Thanks.

Hi @Dana_Arends, unfortunately tags is not supported in the current version. Please vote and leave your feedback here CSV importer: import tags so we can consider this for future enhancements!

1 Like

Hi @TonyC can you help with this please?

Hi there,

I can’t manage to figure out wny my CSV imports will not work. All the column fields in my Sheet are mapped identically to what is required. Can someone help me? This is happening for the last few projects I have created.

Hey @Halley_Bass welcome to the Asana Community Forum :wave:

Can you please provide a bit more information such as what Asana version you are using, if any error message is showing, if something loads and then stops, etc

When you tried to import tasks and as you say it did not work, have you already tried finding one of the tasks you tried to import? As maybe they ended up somewhere else.

I also recommend double checking the filter set in the project, not that some tasks are just hidden.
Screenshot_1253

And I recommend looking through all troubleshootings steps.