Don't force the Form Response Task Type
Alex Rizea
Why do we need to have the Form Response as a mandatory task type?
Most people would be using forms to represent other existing/custom task types. Some Workspaces might not even use forms at all.
There's nothing in the default form settings that would use a specific default task type, and it doesn't default to form response either.
Furthermore, task types can be set at the List level, so it doesn't have anything to do with Forms.
What am I missing here?
Log In
Joshua Borger
I just found this out as well, and I'd like an option to turn off automatically converting form submissions to that "Form Response" task type. For most of our forms, I have task types that automatically set after creation depending on a custom field.
For example, a backlog request gets submitted with the custom field "User Story" selected. Once the submission goes through, I have automations set on my backlog list to change the task type to my "User Story" task type. Now with the "Form Response" task type, I have to add more automations at the form level to make sure that it gets converted to the proper task type, so I'm basically doubling the automations I have to create.
Joshua Borger
Also, for other use cases, it's just more useful for the default from a form to be a task, not a form response task type.