Smart Issue Templates for Jira Cloud
Smart Issue Templates for Jira Cloud
Breadcrumbs

External Data for Jira Fields

Smart Issue Templates works with fields provided by the External Data for Jira Fields app by codefortynine. You can store a value for one of these fields in a template, and Smart Issue Templates applies it when the work item is created.

This page covers what the integration does today, which field types are supported, and where the boundaries are. Use the child pages to set it up and to see the gaps in full.

What the integration does

  • Supported External Data fields appear when you create or edit a template.

  • The value you choose or enter is saved with the template.

  • When the template is applied, the value is written to the new work item.

Two supported configurations


Field Option Sync

External Data Search Field

Jira field type

Select List (single or multiple choice)

External Data Search Field (single or multiple)

How you set the value in a template

Choose from a synced dropdown

Type the value manually

Where the data comes from

A synchronized option list stored in Jira

A live lookup against the external source

Best for

Option lists that are static or refreshed on a schedule

Data that changes constantly

Field Option Sync is the recommended option. Because the app synchronizes the options into a standard Jira Select List, Smart Issue Templates can display them exactly as Jira does, and users pick from a dropdown instead of typing.

Supported field types

Field type

Supported

Notes

Jira Select List with Field Option Sync

Yes

Select from synced options

External Data Search Field (single)

Yes

Enter the value manually

External Data Search Field (multiple)

Yes

Enter each value manually

External Data Asset Field

No

Not currently supported

External Data Info Panel

No

Display only field

Known gaps, in short

The External Data app provides its own search interface on the work item view, and it does not expose that search or its option values to other apps. Three things follow from that:

  • Live search does not run inside a template. A Search Field value has to be typed to match the source exactly.

  • In hierarchies, the dropdown has no options to show, so the field accepts a typed value instead.

  • A typed value cannot be validated against the external source, because the source is not available to Smart Issue Templates.

These are boundaries of what the External Data app makes available, not defects in Smart Issue Templates. The full explanation, including what each one means in practice, is on External Data fields: known limitations.

Next steps