Hi @Frank Petri
You’ve spotted one of the current limitations of native JSM/Jira Forms — there’s no built-in way to pre-fill a field value (especially hidden from the user) on a public form. Every field shown in the form needs to be completed by the submitter, and if you want a constant value like Product Manager = John Smith, you either:
-
Have to include it as a visible, pre-set field in the form, or
-
Add/update it afterwards via automation or manual editing.
Native Jira workarounds without apps:
-
Automation rule – After form submission, set the field value automatically if the field is empty or if the issue meets certain criteria (e.g., request type = “Feature Request” → Product Manager = John Smith).
-
Default value on field (if supported) – For some custom fields, you can set a default in field configuration, but this only works when the field is present in the screen and visible.
If you want to keep the field hidden and still pre-fill it:
With Smart Forms for Jira (developed by my team), you can:
-
Add the field to the form but mark it as hidden from the user, but the values will be still mapped to the fields.
-
Set a default value in the form configuration so every submission includes it automatically.
-
Map it directly to the Jira field so the issue is created with that value already set — no extra steps after submission.
For your case, you could keep “Product Manager” entirely invisible to the stakeholder filling the public form, but every ticket created from that form would already have the correct Product Manager populated in Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.