Support merging request form responses into Description blueprint sections instead of appending

We use request forms for intake into both projects and tasks. When a resulting item is based on a blueprint, the blueprint's content is added first to the item's Description field, followed by the request form's responses (with labels as headers). So we end up manually parsing form responses up into at least one blueprint section and then deleting most of the form response content to reduce clutter in the Description field.

It would be great if instead we were able to specify where in the blueprint content for Description some of a request form's responses would be inserted. And if form responses already captured in custom fields or elsewhere could not be added to the end of Description.

Here's an abbreviated example. Blueprint content first:

- - - -

User Story/Description

Technical Problem or Need

Proposed Solution

Please tell us what you know, so we can improve!

Let me know if this is already possible with existing features! This idea was mentioned by Joshua Haupt during a sprint planning session.