CSV Import to existing Sections

English Forum Product Feedback
21

Very interested in this feature too! Otherwise, the CVS Importer is useless for my team.

2 Likes
23

There needs to be a Section ID and a Task ID, and frankly a subtask ID that are all exportable. And then any NEW item you upload without an existing ID would generate a new section, or task, or subtask. Any EXISTING item you upload with an existing ID would update existing sections, tasks or subtasks.
This is pretty basic stuff Asana.

24

Upvoting because, well, it’s stupid that you can’t do this.

25

any update on this ?

26

Upvoting as well. Hoping there is an update soon as the team is unlikely to adapt this new process if they are not able to upload tasks into the appropriate section…

1 Like
27

Hi Asana team, I am also looking forward to see this feature implemented. I saw the previous threads and this has been requested since Oct’19. I checked today and sections are still duplicating when importing tasks into and existing projects even if the existing section has the same name in the csv file.

3 Likes
28

I believe this feature will ease a lot of pain for setting up initial Sprint plans in Asana , Please help us by including this feature

29

Any updates on this?

1 Like
30

Yeah, I am also looking forward to having this feature

31

So, are we going to be able to import tasks into an existing section? It seems like a basic functionality. If you CAN Import into Existing Projects, why wouldn’t you logically also be able to assign the appropriate Section to the Imported Tasks?

Example: You have a Template Project with Specific Sections. You use the Import Function to bring in Tasks. Obviously they have their place in the Existing Project Template. Now you have a bulk of Tasks with No Section and you have to Manually Drag them around…

Why is this a struggle and not something that obviously was an oversight that needs to be addressed to improve the Experience of your Paid Users?

8 Likes
32

Bumping to the top of the thread again, as this came up for us as a need this morning. Has this been mapped in the product roadmap updates?

5 Likes
33

Any updates here? Looks to be a highly requested feature for more than 5 years…

2 Likes
34

I was able to get the new AI import feature to map to an existing Section, but it didn’t upload any of my custom fields, added all to the description :cry:

35

any update on this?

36

This issue still exists.

37

Garrett here, a Group PM Lead owning our core Project Management features. While my teams don’t own this functionality, I do know the use case and just wanted to chime in to say that it’s on my radar. We appreciate the use case based feedback to help us prioritize!

1 Like
38

Thank you for taking this into account, Garret. I think one of the most common cases is when you need to import updated data from a private project to a project that different people have access to. Both projects share the same field and section structure but have different collaborators. The multi-homing feature is not the best solution in this case because the data in the source project contains subtasks and information that should not be seen by the destination project, so the unwanted information can be removed in the CSV.

Currently, when you import the sections, they are duplicated and have to be removed manually, but if the sections in the destination project have associated rules, the references are broken.

1 Like
39

Thank you so much for the detail @Moises_Trejo! :folded_hands:
This is exactly the level of detail that my teams love. I’m very close to marking this thread as “Considered” given how much I’ve talked about it the last few weeks (and it being high on another list of mine), but still want to learn more.

1 Like