nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Autofill Forms Options

GlenellRosburg

I would like to build a form for users to submit requests to my work team. I have several fields that are required by my workspace. I would like these fields to be auto filled so that the end user does not need to select the appropriate option. This will eliminate the possibility of the end user selecting the incorrect option. Is there a way to autofill the required fields?

For example, I would like to have "All" selected as the Client for each request submitted through this form.

Accepted answers

Trudy P Claspill

Hello @GlenellRosburg

What type of project does this concern? Get that information by clicking on the ... button next to the project name in the left sidebar.

Screenshot 2025-09-05 at 10.03.44 AM.png

In what manner are you making the fields required? Did you set that in the Field configuration at the project level? Are you using a validator in the workflow?

If you want the field value to be "All" always why do you need to have the field on the form at all? You could instead set the default value for the field as part of the field context/configuration and then not include the field in the form.

Olha Yevdokymova_SaaSJet

Hi @GlenellRosburg
1. Default Values

You can use default values for some fields in native Jira or JSM forms (like setting "Client" = "All"), but:

The user can still see and change the value.
It works best if you're just trying to reduce mistakes, not enforce logic.

2. Smart Forms for Jira

With Smart Forms for Jira, developed by my team you’ve got more flexibility:

You can set default values for any field — and that default applies only in that specific form (not globally).
You can also make fields hidden with pre-filled values, which means:
- The end user doesn’t see it.
- The form stays short and clean.
- You still capture the right info and map it to the Jira issue on submit.

This is super helpful when:

You don’t want users messing with routing or internal categorization fields.
You want to standardize submissions.
You're working with external requesters who shouldn't have to deal with complex forms.

All comments

Trudy P Claspill

Hello @GlenellRosburg

What type of project does this concern? Get that information by clicking on the ... button next to the project name in the left sidebar.

Screenshot 2025-09-05 at 10.03.44 AM.png

In what manner are you making the fields required? Did you set that in the Field configuration at the project level? Are you using a validator in the workflow?

GlenellRosburg

@Trudy P Claspill We're on a Company-managed project.

The fields are required to be filled in with a drop-down selection option when new stories are created.

Hmmmm... I'm not sure how to set the default value. Would the default value be set only for this form or for all stories that are created? The field should only default to "All" if the user is completing this specific form. If the user is completing a different form, the value may be an option that needs to be selected.

Thanks for helping me through this.

Trudy P Claspill

Setting the default value for the field in the field context/configuration would apply to all issue types in the project that use that field, so that would not satisfy your needs.

In what manner are you making the fields required?

Did you set that in the Field configuration at the project level?
Did you set the field to Required within the Form?

Are you supporting the creation of the issue both through Forms and directly in the Jira UI?

If so, do you need the field to be required regardless of which method is used?

If so, here is a possible work around:

You could have another unique issue type in the project created by the use of this specific form.
Rather than including the Client field in that issue type, you could create an Automation Rule that would be triggered by the creation of that unique issue type.
In the Automation you could then change the issue type to Story and set the Client field to All.

GlenellRosburg

1. Yes, the Field configuration is set at the project level for stories.

I like the idea of creating the a new issue type and then changing it to a Story to set the Client field to All. I will try this.

Thank you!

Olha Yevdokymova_SaaSJet

Hi @GlenellRosburg
1. Default Values

You can use default values for some fields in native Jira or JSM forms (like setting "Client" = "All"), but:

The user can still see and change the value.
It works best if you're just trying to reduce mistakes, not enforce logic.

2. Smart Forms for Jira

With Smart Forms for Jira, developed by my team you’ve got more flexibility:

You can set default values for any field — and that default applies only in that specific form (not globally).
You can also make fields hidden with pre-filled values, which means:
- The end user doesn’t see it.
- The form stays short and clean.
- You still capture the right info and map it to the Jira issue on submit.

This is super helpful when:

You don’t want users messing with routing or internal categorization fields.
You want to standardize submissions.
You're working with external requesters who shouldn't have to deal with complex forms.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud