Currently, it is possible to create Custom Fields that are assigned to specific Task Types. However, Forms do not allow:

selecting a default Task Type for submitted tasks;

displaying or using Custom Fields that belong to a specific Task Type.

This creates an inconsistent experience because Task Type-specific fields can be configured in the workspace, but they become unusable when creating Forms.

Current Behavior

A Custom Field can be linked to a Task Type.

When creating a Form:

there is no option to assign a Task Type to the Form;

Custom Fields associated with that Task Type are not available to add to the Form.

As a result, it is impossible to create a Form that fully supports a specific Task Type.

Expected Behavior

Forms should support Task Types by allowing users to:

select a default Task Type for all tasks created from the Form;

automatically display Custom Fields associated with the selected Task Type;

optionally filter the available fields based on the selected Task Type.

This would make Forms consistent with the Task Type configuration available elsewhere in the product.

Why This Matters

Without Task Type support in Forms:

Task Type-specific fields cannot be collected through Forms.

Users cannot build Forms tailored to different workflows.

Existing Task Type configuration loses its value in one of the primary task creation methods.

Users are forced to rely on manual updates or automations after form submission, even though the Task Type is already known beforehand.

Suggested Implementation

When editing a Form:

Add a Task Type selector in the Form settings.

Once a Task Type is selected:

automatically make its associated Custom Fields available in the Form builder;

optionally pre-populate the Form with those fields.

Every task created from the Form should automatically receive the selected Task Type.

This would eliminate the current inconsistency and allow Forms to fully support Task Type-based workflows.