I have a question regarding the use of forms in Asana:
I’d like to use forms to gather feedback after completing specific project phases (Leistungsphasen). The idea is that each project contains its own form. Once a certain phase is completed and the corresponding milestone is reached, a rule triggers a task that asks the user to fill out the form.
Now my question: Since forms are project-specific, is there a way to collect all responses centrally in a separate, independent project – regardless of which project the form belongs to?
Has anyone found a solution or workaround for this?
Hi @Viktoria_Krebs , if you are asking the same set of questions for each project and its phase, then it makes sense to create one form for all projects/phases - that will be low maintenance.
To differentiate the answers, so that you know which project and phase it relates to, just add a couple of single-select questions to be filled out by the submitter. You can then leverage those fields to Group by or to filter Dashboards - keeping those single-select fields could be high maintenance, depending on the frequency of your project creation. It also assumes that you use the same names of Phases for all your projects.
Adding to @Richard_Sather excellent advice I’d add that this is possible:
Create a rule along these lines:
When a task is added to this project
check if it is {form submission}
add to {central project}
You can add this rule to your template project.
Be warned! This should accomplish exactly what you’re asking, although I’d be hesitant to implement this. If possible, I would go for Richard’s option, as it introduces less redundancy and leave you more flexible. Some related reading: As expected, everything went differently.
If you have Enterprise(+), adding this rule to a bundle (and having it triggered by tasks added to a bundle’s section) would be only slightly better as the forms are still redundant.
Be warned! This should accomplish exactly what you’re asking, although I’d be hesitant to implement this. If possible, I would go for Richard’s option, as it introduces less redundancy and leave you more flexible. Some related reading: