We have a project called “New Enquiries” where all sales leads go, each task has details of the client and the steps taken to convert it into a live project (e.g client meeting and phone call sub tasks).
When the task is converted and moved to a new team we would like to keep the original task as a task at the top of the new project so all the info is more readily available.
I can do this manually by going back to “New Enquiries” and making the greyed-out task back into a task and then moving project, but can this be automated?
Thanks,
Rob.
HI @Rob_Nabney 
Thank you for reaching out!
What a great question! Unfortunately, I believe that the only way to achieve this is by manually adding the task following the steps you have explained.
Please note that when converting the task into a project, the task description is converted into the project description. This could be very useful to have all the important information about the Project in its details.
Have a great day Rob! Please let me know if there is anything else I can help you with!
Just checking if there has been any update on this in the last year.
We have a project for “Requested Projects” where we use the task form to capture enough information to help us vet and prioritize the project. When a project is green-lit, we use the “convert to a project” feature, however, the initial task is marked complete and very hard to find on the new project. Is there anyway to either use “Convert to a Project” where the original task is not marked as complete, OR, is there a way to write a rule to unmark the task as complete when using “Convert to a Project”?
Thanks!
1 Like
We have an intake project to manage/initiate the marketing onboarding process for new physicians and providers in our health system. On the intake project side, we have a few sections where there may or may not be discussion around something prior to the onboarding project is created by converting the original task to a project using a template.
Is there any way to have that original (now “closed” task) be added to the newly created project? It not only provides good details in the project view for the onboarding information but if it’s not moved to the new project, you lose the context of all the comments and changes the original task went through.
Right now we just manually add it once the project has populated, but that can get really tedious when we’ve got 15-20 open tasks in the intake project at any one time.
Hi @billyadams , are you ok if I merge your post into this existing thread?
Yeah, I guess that’s a logical merging. Might need to end up submitting a product feedback thread on this. There’s a number of things that are not ideal in the way the task → project conversion process works. It’s been getting better though.
Do you know if this is possible via a script rule? We are looking at enterprise in our next renewal cycle and scripts are one of the things I’m looking forward to actually getting to try.
Hi @billyadams, I have merged into this existing thread, reopened it, slightly rephrased the title and converted it into a English Forum > Product Feedback request so you and others can now vote on it. I did!
It is likely possible with a script rule, yes. But you would need the script to emulate the entire convert task to project procedure since it is not available as an API call. My developers managed to do it for another customer of ours but they didn’t want the initial task in the project, although I don’t see why not add that at the end of (a very long) script.. just need to looks out for timeout issues. Asana like the scripts to run fast and furious!
If you are looking to upgrade, hassle-free, to Enterprise while gaining an Asana Partner like us by your side as an added bonus (providing better support and complimentary check-ins calls) feel free to DM me for details. 