When an organization starts looking at forms in Asana, that usually opens up a new world for them. I think this is one of the most underused features of Asana, to be honest!
But at one point, managing several forms could be complex. And it is even more complex to keep track of all the forms, where they are, and what is the link to share them.
A solution is to merge several (simple) forms into a new one. The trick? Add a first question in the form, being Ā« What is your request regarding? Ā» and based on the answer from that drop-down, use the branching mechanism to show the appropriate next questions. Then use Rules to move the submission into the right project so the right team is notified.
PS: this idea was initially shared by @lpb on the forum!
Forms are such a powerful Asana feature; I concur, @Bastien_Siebman.
Form branching is a Business plan feature so thatās required to use this tip, as I point out here:
Iād combine forms sparingly anywayāsure, if theyāre related then branching may be reasonable and natural, but even with the Business plan I think itās more complicated to do this for otherwise unrelated forms.
As all the ASANA experts are gathered here, maybe I find a solution for my actual problems with form branching:
We set up a form as a ticket system for all the inputs and request for all departments of our company. As we realized that the request differ from department to department we want to specify our form.
IT and media have similar requests, business relations and customer support have similiar requests and our product manage department has its special request.
Now I got stuck with two diffrent limitations in ASANA:
it is not possible to combine 2 answer possibilities in one branch
I canāt use customized fields twice - if I use it in one branch, I canāt select it in another branch
Is there any solution out there?? Do I miss a certain feature??
Thanks in advance
ĪĪ¹ @anon81228582 , if I have understood your scenario correctly, if you use a single-select field in a branch and then add the same field to another branch it will NOT show up in the āAvailable fieldsā part of the āConnected toā list. However, if you scroll down to the āAlready in useā part of the āConnected toā list you can still select the custom field you want, even if it is in use. Asana will simply have a warning triangle saying that it will essentially overwrite the first entry with the next.
However, this is not necessarily an issue if you use the same single-select field in more than one branch within the same primary question, as long as the path of your formās branches will lead the submitter to select from this field only once.
If for some reason you cannot do that, then the below example concludes with a workaroundā¦
Say you have a āUniverseā single-select field which is connected to the options that each are a branch to a further question related to that āuniverseā
If āStarwarsā is selected then within its branch you can have the following question that draws from the āJediā field for answers on peopleās āfavouriteā choice
But if āStarwarsā is selected and then you also have a 2nd question within that same branch, you can still use the same (Jedi) choices as you did with the first question, which may make sense, however this will clearly create a problem for your results (as the yellow triangle icon will note).
The form will overwrite the choices for āfavouriteā with the choices for āleast favouriteā because you are using the same Single-select field for both answers. To solve this, you can (manually) create a duplicate of the āJediā single-select field (with the same options) and rename them both these fields to āFavourite Jediā and āLeast Favourite Jediā respectively so you can collect the correct answer to each question separately.
