How to use the Advanced Configuration

Readonly fields support three display type options:

• Simple select

• Multi select

• Autocomplete

Open

The General tab configuration settings for readonly fields

Editable fields use the Generic display type exclusively.

Open

The General tab configuration settings for editable (Generic) fields

SQL Database Source

Dropdown menu

Determines which data source the field uses for retrieving data. Data sources must be preconfigured before they appear as selectable options. 

Auto Search

Toggle switch

Automatically triggers search when users open the Search dialog, using values already present in the field.

Hide Column Labels

Toggle switch

This toggle controls the visibility of column labels when the field is displayed. Enable it to hide labels in the field rendering.

Open

This screenshot shows a custom field with column labels and hidden column labels

Use Auto-Bind

Toggle switch

Automatically recalculates field values when dependent fields change. If your field depends on other fields, enabling this setting intercepts changes in those fields and triggers value recalculation.

Refresh Type

Dropdown menu

Controls how and when the field refreshes data from the source database. Choose an option based on how frequently your source data changes:

• NEVER: Field data never updates, even if the source database data changes.

• ALWAYS: Field data updates every time it's viewed by querying the database. Use only for frequently changing data, as this can impact system performance.

• EXPIRES: Field data updates after a specified time interval (for example, "1w" for weekly, "1d" for daily). Use standard Jira time interval format. This option provides better performance than ALWAYS while keeping data reasonably current.

Security Type

Dropdown menu + Toggle switch

Combines action capabilities with permission settings to control what users can do with the field and database. You configure both which actions are available and who can perform them.

Open

This screenshot shows a combination of an action and a permission setting

Security type (permissions):

• ALLOW ALL: Users can perform all database actions.

• DENY ALL: No users can perform any database actions.

• FIXED: Configure permissions for each action independently.

• DYNAMIC: Use custom scripts to determine permissions based on issue context or Jira environment variables. See the How to write Security scripts page for details.

Actions:

• Allow Set: Users can search and select values. Triggers the SEARCH and SET scripts. If enabled, a dedicated Search icon appears in the field's Actions panel.

• Allow Insert: Users can add new values to the connected database table. Triggers the INSERT script when completed. If enabled, a dedicated Insert icon appears in the field’s Actions panel.

• Allow Update: Users can modify existing values in both Jira and the connected database table. Triggers the UPDATE script when completed. If enabled, a dedicated Update icon appears in the field’s Actions panel.

• Allow Delete: Users can remove data from both Jira and the connected database table. Triggers the DELETE script when completed. If enabled, a dedicated Delete icon appears in the field’s Actions panel.

Open

This screenshot shows the actions' icons in the field’s panel

For fields Display Type set to Simple select, Multi select, or Autocomplete, only two columns should be configured:

• One field acts as the primary key;

• The other field contains the data displayed by the field.

  Open

  

  Column list configuration for a readonly field

For fields with Display Type set to Generic, multiple columns can be configured to provide full functionality.

Open

Column list configuration for an editable field

Physical Name

Specifies the exact column name as it exists in the database table.

Label

Defines the display name for the column in Jira's interface. This setting only applies to Generic Advanced Row Fields, as readonly fields don't display column labels. Label visibility is controlled by the Hide Column Labels setting in the General tab.

Type

Specifies the column's data type for validation and indexing purposes. Available options include BOOLEAN, NUMBER, REAL, STRING, DATE, DATETIME, and SEQUENCE (for auto-generated primary keys). The selected type determines which constraints are available and enables appropriate JQL search operators.

Default Value

Sets the initial value that appears in the Insert form's input field for this column.

PK

Identifies this column as the primary key in the connected database table.

Searchable

When set to Yes, this function makes the column available in the Search dialog, enabling its value to be used in SEARCH scripts.

You can also streamline single-column searching by designating one column as Autocomplete. Autocomplete columns have additional configuration options (like minimum character requirements) accessible through the adjacent Settings icon.

As illustrated in this screenshot, when any column is set to Autocomplete, all other columns' Searchable settings are automatically reset to No.

Open

Column configuration showing an Autocomplete searchable setting with an active Settings icon

Required

Makes the column mandatory for INSERT/UPDATE operations. Required columns display an asterisk (*) next to their label, and users must fill the corresponding input field before submitting forms.

Constraints

Defines validation rules that input data must satisfy before values can be saved. These conditions ensure data integrity and enforce business rules.

Support a limited set of operations: DEFAULT, GET, and SEARCH.

Support the complete operation set: DEFAULT, GET, SET, INSERT, UPDATE, DELETE, SEARCH, and SEQ.

The Scripts configuration interface uses SQL syntax by default, shown by a small indicator icon next to each operation.

You can switch to SIL scripts by right-clicking any operation.

Color-coded operation labels show configuration status (green for configured, red for missing). You only need to configure the operations you plan to use.

Selecting any operation opens a Details panel with additional configuration options.

Each script can use additional parameters from Jira screen fields or issue fields (both standard and custom).