Task Requirement Rule

Add one more table to the design.

Parents Table,  lets call it Customer Complaints

Issue Table

Issue Tasks Table

Customer Complaint Tasks 

When you set the Issue for a particular Customer Complaint, fire a pipeline that will search for the Issue Task for that Issue.

The create a Complaint Task record for Issue Task

So if your Issue was something like "Customer wants a refund"   The Issue Tasks might be 

Send RMA

Inspect Return

Credit Customer Credit Card

All three tasks are now child records of the Customer Complaint record. 

There are a few routes for this. 

One is to generate a connected, but empty-Task that needs to be completed after it has been created using a Pipeline which requires the user to Save & keep working; and then wait for that record to appear (not ideal). 

A second is to have the User populate necessary Fields with the data entry values necessary to be generate a complete child-Task record without further update being necessary, and make those fields required when the [# of Tasks] = 0; so that they must fill these in before saving the parent-record.  Your pipeline will then trigger on-save and generate the child-Task as well as empty out the parent-data fields that were used by the Pipeline.  You can then generate a Report and a second Pipeline to look for records which failed to generate the child-Task (for whatever reason) and use the data to generate the missing record.  In both cases; your data-entry fields would be empty at the end of the process validating the successful generation of the child-Task record required.

Form rules can't require a child row, and blocking the save doesn't work either. On a new record, the embedded Task table only becomes usable after the parent is saved. Here are a few patterns that do work.

Auto-create the tasks. Don's template-table idea is the standard approach: keep Issue Task templates, and when the Issue Type matches, a pipeline searches those templates and creates a related Task for each one.

If you only have a few task types, skip the template table and build each option right into the pipeline, with one branch per Issue Type and a Create Record step in each.

Another option is a few formula fields on the parent that work out the new task name from the type. The pipeline then uses that value to create the child task.

Enforce it at the next step instead of at save. Let the parent save, then block moving to Submitted while Task Count (a summary field) is 0. You can do that with a custom data validation rule on the status change, or a formula button that only appears once Task Count is above zero.

Capture the first task on the parent. A required "First Task" field on the parent form, plus a pipeline that turns it into a child Task after save.

Make it visible. A formula banner on the form or a "Missing Tasks" report flags parents with no tasks, so someone follows up.

https://help.quickbase.com/docs/generate-template-records-with-pipelines 

https://help.quickbase.com/docs/create-a-summary-field 

https://help.quickbase.com/docs/building-form-rules-in-quickbase