When a task with files attached is converted into a project the files do not translate to the new project. All other task details are added to the overview tab but the files are no where to be found. It would be great if the files could be added to the key resources section on the overview tab or in the files tab within the new project.
Our marketing team takes in creative requests which often includes a file but when they convert the task into a full project to manage the many parts of the request they loose any of the attachments which is needed for the project work.
15 Likes
Good idea. Make sure to upvote your own post.
Hi, Just looking at this for incoming project requests with associated files. Do you know where the files go ?
I can not understand the logic of not porting over the files when I task is converted to a project. This is a huge development miss.
We’re testing the use of Asana forms as an intake for project proposals. Right now I have a rule that will convert the proposed project (represented by a task) into a project when the proposed project status is marked Approved via a custom field I created. So, not having the supporting project documents follow it is an issue.
I know that this is in the Feature Request phase, but honestly, this feels way more like a bug than a new feature being requested. Expected, logical behavior would for the files to be added to the project level since everything else is added to the project.
Also, not just files, but the conversation around the previous task should be brought over. The only work-around (other than re-posting all the comments and re-uploading all the files) I’ve found is to simple add the closed/converted task to the new project.
1 Like
Agreed with all above. I have created a step in my workflow to move this task (that was converted) into the new project to act as the “Brief” for the project. Moving the task into the project also moves the associated files into place. Would be great if this movement happened automatically.
Huge +1 on this request.
@Beth_Seeber - could you share insight into how you accomplished this? Did you use a native rule, or are you scripting this in an external system? Natively in the platform, I haven’t figured out how to add this task to a project in a rule since it doesn’t “exist” yet until after the rule runs.
While I have automated quite a bit of steps, this “kick-off” is otherwise a manual process:
-
AUTOMATION: First a form submission creates a task in my Ops Intake project, and a rule triggers to assign to me for notification, and to multi-home the request in our Planner project
-
MANUAL: I review the task/request for clarity, and move the task/request to an “Assign to Team” section
-
AUTOMATION: This “assign to team” section uses a rule to move this task to our Content Review project, and custom fields/triggers determine which team member to assign to the request to respective Content team member for approval/acceptance of the project.
-
AUTOMATION: When the Content team moves this Request task to section “Approved”, convert to a project using [this] template, assign a due date (if one is not specified from the request), add the new project to [this] portfolio(s), remove from the Content Planner project and add to our Content Calendar project, and reassign the “Request” task to myself so that I get an alert to perform next steps
-
MANUAL: I rename this “[Converted to Project]…” task as “[BRIEF]…” and manually move the task out of the Content Requests project and into the newly created project. Our teams and vendors know that this [BRIEF] task is to serve as the project charter for the work to be done, and all general project communication takes place within the comments of this task.
Hope that’s clearly written and you can follow along 
Happy to dive in more if needed.
2 Likes
Thanks for the great writeup! This is in line with what we’re doing (generally) as well; I was hoping that last manual step could be automated natively but seems not (yet).
This is very needed for my org as many workflows start with an Asana form. Voted and hope this gets addressed
This is definitely a major failing on the part of Asana. it almost defeats the process of having an intake form.