It would be great to add a ‘project’ fields type to forms with the functionality.
Rule functionality: new task from form to be multi-homed on project entered during form submission.
I came to to the forum looking for this exact solution. Is there a way to allow a drop down/pick list to appear in a form so that anyone submitting a form can link the project before hitting submit?
2 Likes
Hi there! Is there a way to pull my team project list or a portfolio project list into a task intake form? My intake form will collect tasks for multiple projects, and I’m worried a free-type field will lead to errors in project assignment. Is there a way to make this a dropdown/typeahead field?
2 Likes
I have a form I’ve created for our manufacturing Design Team to use to request paint finish samples from our paint booth. The form lives in a specific project called “Finish Samples” and they are managed there via board view through their production process (they can be very complicated finish processes, and this board view works wonderfully).
Here’s the weak spot in it. I need an AUTOMATED way of making sure every one of these tasks ends up living also homed in the project for the job it represents. I need there to some line somewhere in that Form asking it “What Project does this need to be added to?” and allow them a live search-function type field. Or at the very least, the ability to copy/paste the web address of the project.
All of our manufacturing jobs have their own individual projects. Is there any way at all I can give our Design Team the ability in the form to answer a question that will multi-home this task into whatever project it represents?
As a side note, I know it’s not hard to manually add this to another project. This just fits the category of one of those things that really needs NOT to be yet another addition to someone else’s massive checklist.
I used to have this Form built in to the Project Template all these jobs get created from. However, because of limitations in Asana, this ended up being a horrible idea, because we changed some of our company structure/workflow that necessitated changes to the Form, and I would have had to edit HUNDREDS of forms in hundreds of projects. So I just emailed the whole company and told them to quit using the embedded form, and instead use the new form that’s central to the whole company.
I really wish there was a way Asana would allow us to manage forms on the Team level. Or perhaps even on the Portfolio level.
3 Likes
+1
Hope this becomes an option soon.
Airtable allows forms to contain select list data like this, which is a big plus.
Until Asana implements this feature, we’ll keep multi-homing manually.
1 Like
Note: Not a solution but marked as such to elevate a key reply
Hi @as_an_android , instead of manually multi-homing your tasks, you could create a single-select field connected to a question in your foem, that lists your projects as options.
Then create one rule with ‘otherwise if’ conditions based on a selected project from that single-select field/question, which would then add/move the task to the relevant project.
So instead of manually multi-homing tasks to projects, you would then need to manually maintain the options in your single-select field, whilst also maintaining that related rule. I think you will find the latter to be far less manual work, depending on the frequency of projects being created VS form submissions.
PS: IMO, the reason Asana does not support this (and may never do) is due to privacy. Listing all of one’s project in a public form could be a potential data leak. The same applies for a People field.
1 Like