Supported fields

Issue Templates Agent supports an extensive range of standard, custom, and third-party fields, ensuring that every Jira ticket template remains as functional and detailed as a manually created task.

If a field is not listed in the table, that means that it is not supported as if this moment.

Supported system fields in creating Jira issue template

Field	Parent template	Child template	Subtemplate
Actual end	✅	✅	✅
Actual start	✅	✅	✅
Affected versions	✅	✅	✅
Attachments	❌	❌	❌
Approvers	✅	✅	✅
Assignee	✅	✅	✅
Change reason	✅	✅	✅
Change risk	✅	✅	✅
Change type	✅	✅	✅
Components (Jira)	✅	✅	✅
Description	✅	✅	✅
Due date	✅	✅	✅
Fix versions	✅	✅	✅
Flagged	✅	✅	✅
Impact	✅	✅	✅
Issue links	❌	✅	❌
Labels	✅	✅	✅
Parent	✅	Filled automatically
Priority	✅	✅	✅
Reporter	✅	✅	✅
Security level	❌	✅	❌
Sprint	❌.	✅	❌
Start date	✅	✅	✅
Story points	✅	✅	✅
Summary	✅	✅	✅
Team	❌	✅	❌
Watchers	❌	✅	✅

Team field requirement

The Team field requires the user to provide the ID of the team. Because of technical limitations, the app does not support the typical select functionality for this field.

Supported custom fields in creating Jira issue template

Field	Parent template	Child template	Subtemplate
Cascading select	✅	✅	✅
Checkboxes	✅	✅	✅
Date picker	✅	✅	✅
Date time picker	✅	✅	✅
Multi select	✅	✅	✅
Multi user picker	✅	✅	✅
Multi group picker	❌	✅	✅
Multi version picker	❌	✅	✅
Number	✅	✅	✅
Paragraph	✅	✅	✅
Project picker	❌	✅	✅
Radio buttons	✅	✅	✅
Single select	✅	✅	✅
Single user picker	✅	✅	✅
Single group picker	❌	✅	✅
Single version picker	❌	✅	✅
Short text	✅	✅	✅
URL	✅	✅	✅