Auto-Fill Fields with Default Template

Automatically populate the Create Issue form using default templates configured per project and issue type — speeding up issue creation and enforcing consistency across teams.

Automatically prefill Jira’s Create Issue form with values defined in a selected template — based on the current project and issue type. This feature helps enforce standards, reduce manual input, and guide users through the issue creation process.

---

⚙️ How It Works

Templify allows you to assign an issue template as the default for a specific combination of project and issue type. Once configured, the moment a user opens the Global Create Issue form in Jira, Templify will:

• Automatically locate the matching default template

• Instantly prefill the issue form with the template’s field values and dynamic expressions

No manual clicks. No field-by-field entry. The form is ready to review and submit — pre-validated, pre-aligned with your team’s standards.

---

🔄 Flexible Template Mapping

One issue template can be reused across many contexts. For example:

• Use the same onboarding template across multiple HR projects

• Apply a single bug report structure across various support teams

• Set different defaults for “Epic”, “Story”, or “Bug” within the same project

Templify’s smart assignment system allows a single template to serve multiple project + issue type pairs, making your templates modular and scalable.

---

🧪 Interactive Demo

In the interactive demo below, you’ll learn how to:

1. Assign a template as default for a project and issue type

2. Open the Global Create Issue form

3. See the automatic population of field values in action

This feature requires no user interaction on the form — the prefill happens automatically in the background before the screen is rendered.

---

📋 Supported Fields

The following fields are currently supported when using default templates to prefill the Create Issue form:

Field	Description
summary	Issue summary
description	Issue description
assignee	Assignee
reporter	Reporter
priority	Priority
labels	Labels
duedate	Due date
parent	Parent issue (for sub-tasks)
components	Components
fixVersions	Fix versions
versions	Affects versions
status	Status
resolution	Resolution
timeoriginalestimate	Original estimate
select	Single select (custom field)
radio	Radio buttons (custom field)
url	URL (custom field)
paragraph	Paragraph (multi-line text)
multiselect	Multi-select (custom field)
userpicker	User picker
multiuserpicker	Multi-user picker
textfield	Short text field
checkboxes	Checkboxes (custom field)
people	People field
date	Date picker
targetStart	Target start date
targetEnd	Target end date
datetime	Date & time field
number	Number field
cascadingselect	Cascading select (custom field)

ℹ️ Field Compatibility Notice Templify supports all standard and custom fields that are currently available for manipulation via the Jira Cloud platform. Some advanced field types are not yet supported by Jira APIs for default prefill — but as soon as Atlassian makes them available, Templify will fully support them.

---

✅ Why Use Default Templates?

Using default templates for issue creation offers several key benefits:

• Consistency: Ensure every issue starts with the correct structure, fields, and standards

• Speed: Eliminate repetitive typing — especially useful for frequently created issue types

• Guidance: Help new or occasional users by pre-populating the data they need to provide

• Accuracy: Reduce human error and the risk of incomplete or misconfigured issues

This feature is ideal for standard operating procedures, recurring work, and any team looking to improve quality at the source — the Create Issue form.

---

📌 Best Practices

• Assign default templates to your most frequently used issue types

• Use generic default values in your templates for fields that require user input in specific cases (e.g., a generic summary like “Bug in [module]” or placeholder acceptance criteria in Stories). This ensures the form is complete, but still encourages users to refine the content before submission.

• Use dynamic fields to adjust content based on user or timing context

• Combine with the Issue Template picker for optional override flexibility