Hello!
Please help with this issue. What format and structure should the csv-file have so that when it is imported into Asana, the tasks will be marked as completed?
Hi,
I am not sure this is possible with the CSV importer. @LEGGO any idea?
According to my understanding importing from csv will not update the current tasks but will create new ones.
see this thread:
Hello @Marina_Moskaleva ,
Welcome to the Asana Forum 
As of today you cannot import tasks as completed or match them to existing completed tasks. You can upvote the thread that Paul shared, the more votes, the more likely it is that the feature request will be prioritized.
May I ask you what your specific workflow, in this case, is and why do you need to import completed tasks? Maybe there is another way to achieve this efficiently.
Are you already aware of bulk actions? You can complete up to 50 tasks simultaneously with just a click.
Cheers,
Rosario
Do you have any recent developments to share regarding this matter? I’m currently in the process of importing a substantial volume of tasks, and it would be highly beneficial if they could be pre-completed upon import. Presently, I find myself manually completing 50 tasks at a time, and any improvements in this workflow would be greatly appreciated.
No news on this topic I am afraid.
Hi @steven_lu , I’ve tested this and it works:
In your destination project, where you will import your CSV, prepare it with the following:
-
Create a ‘status’ single-select field with the a single option ‘complete’ (or better yet, add an existing status field from your field library if you want the value to remain on your tasks, after importing).
-
Create a Rule that when tasks are added to the project, check if ‘status’ field is complete, then change task completion status to complete AND clear ‘status’ field (skip this AND step if you use a status field from your library and you actually want the ‘complete’ value to remain on your tasks).
Then, in your CSV file, BEFORE you import it, add a column called ‘status’ and add the value ‘complete’ for all tasks you want to be imported as complete. (or use the relevant value from your status field in your library, which could be eg. ‘Done’).
During the CSV import, choose ‘Make changes’ to make sure your status field in your CSV is correctly mapped to the status field in the destination project.
Once the project is imported, the rule should fire and you can remove/delete the status field from the project (or keep it if you have used a status field from the library and you want that value to remain on all tasks).
1 Like
Are we sure rules fire on CSV import? A little voice in my head is telling me someone pointed out it doesn’t…
Yup, tried and tested 
After testing this, the Rule seems rather inconsistent, and does not complete all tasks even though the status is set to complete. Is anyone else experiencing this?
attaching an image of the test batch of 55. 7/55 were not triggered
Ah that’s a shame. I admit I have tested this on a much smaller batch without any misfires.
Good to know and look out for it!
@Bastien_Siebman , is this what you were referring to above? i.e. an inconsistency of rules being triggered?
I had a similar issue when bulk-editing tasks where an edit would fire a rule: out of 200-300 tasks, 2 or 3 would not fire the rule 
My point was more that the CSV import was not firing at all, but looks like this was either not true or fixed.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.