Prefilling the issue creation screen

When to prefill instead of create directly

The default Issue Templates flow creates the new Jira issue immediately, with the template applied. That is the right behaviour when the user can be trusted to fill the variables correctly and there is no need to review.

When you want the user to review or override values before the ticket is created, switch to the prefill flow. The prefill flow opens Jira’s native create-issue dialog with the template values pre-populated as defaults. The user can tweak any field, then submit through Jira’s standard flow.

How to use the prefill flow

The steps are the same as the normal create-issue flow, with one substitution:

• Open the Apps menu.
• Pick Create issue from template.
• Pick the template.
• Click Prefill new issues instead of Use this template.

Choose Prefill new issues to route the template through Jira’s standard create dialog instead of creating the issue directly.

Jira’s native create-issue dialog opens, every field pre-populated from the template. Fill or adjust as needed and click Jira’s standard Create button.

Jira’s standard create dialog opens with template values as editable defaults, ready to confirm or override.

When the prefill button does not appear

The prefill action is hidden in two cases:

• The template contains multiple issues, like an Epic with Stories or sub-tasks underneath. Jira’s native create-issue dialog handles only one issue at a time, so prefilling a multi-issue template would lose the sub-tasks. Use the direct create flow instead.
• The template has required variables. Jira’s native create-issue dialog does not have a way to enforce variable input, so the prefill flow is hidden to avoid producing tickets with missing variables. Make the variables optional, or use the direct create flow.

In both cases, the template still works; only the prefill action is unavailable. Pick Use this template and the create flow runs normally.

When prefill makes sense

The prefill flow shines for:

• Single-issue templates where the user expects to confirm.
• Templates with many optional fields the user often customizes.
• New team members who are still learning your conventions and want Jira’s standard create screen as a familiar checkpoint.

For high-volume, fully automated cases (incident reports fired from PagerDuty, onboarding tickets fired from a CRM), prefer the direct create flow or the Jira Automation integration.

Related guides

• Creating issues from templates for the standard direct-create flow this page builds on.
• Creating variables in templates to understand why required variables hide the prefill action.
• Automation integration for unattended, high-volume ticket creation.