How can we set or enforce the Parent (Epic Link) field when creating a Technology Design Decision (T

neeru nayar

I am configuring a Jira Form to directly create Technology Design Decision (TDD) work items. The TDD issue type has the Parent (Epic Link) field marked as required.

When attempting to add and link the Parent/Epic Link field in the form, it is rendered as a URL field, and validation requires a URL instead of accepting a valid issue key (e.g. RDOF-2267). As a result, the Parent field is not correctly populated, and form submission fails with the error: “Field Parent is required.”

Automation is not a viable workaround in this case, as the issue is not created due to validation failure.

Could you please advise:

• Whether Jira Forms supports setting the Parent/Epic Link field correctly during issue creation
• If not, what the recommended approach is when Parent is a required field
• Whether there is a way to prepopulate or default the Parent value within the form

Thanks

Ajay _view26_

Hi @neeru nayar 

What you’re seeing is consistent with a Jira limitation rather than a simple configuration mistake.

If the field is rendering like a URL input instead of accepting an issue key, I would treat that as “Forms does not currently support this field correctly for this use case” rather than something you can fix with field configuration alone.