The different field types

Table of contents

Live or Snapshot field?

Elements Connect fields are grouped in two categories: Snapshot and LiveThis sections explains the difference between them and help you decide which one you should use, according to your needs.

The main difference between a Snapshot and a Live field is when they fetch data from their datasources.



Snapshot fields get data from their datasource only when they are editedWhen they are displayed, the data is read from Jira database.
Unlike Live fields, they store their display value in Jira database and their display is the same in all views.

You can update the value of a Snapshot field:

  • by editing the issue
  • with an Elements Connect post function
  • using Elements Connect action in Automation for Jira


Live fields get data from their datasource when they are edited and displayed.


Let's say we want to store an exchange rate in a Connect field.

Every day, this exchange rate changes, this table shows the value displayed according to the field category:

TimeOfficial exchange rateSnapshotLive
Issue creation1.101.101.10
+1 day1.121.101.12
+2 days1.171.101.17

Main differences

Always display up to date information



Ease of configuration


Because of their simplicity, snapshot fields require less configuration work than live fields


Depending on your needs and the datasource you're using

Impact on performances


Datasource is called only when the field is edited


Datasource is called every time a Live field is edited or displayed.

Depending on how fast the datasource is, it can have impact on the performances.

See Improve performances.

Single value



Multi values



Different edit and display rendering



Can be used as dependency


Because Snapshot fields do not store a key, when they are used as a dependency in another query, they are evaluated to their display value


Compatible with third party app



Because of the storage format of the Live fields, not all apps are compatible with Elements Connect Live fields.

To be compatible, they should use the Java API.

Field names in v5

With Elements Connect v6, fields have been renamed, the following table lists the changes:

v5 namev6 name
StandardLive Text
UserLive User
DeprecatedLive Text (legacy)
DateSnapshot Date
DatetimeSnapshot Datetime

The Snapshot Text field is a new feature of Elements Connect 6.

The different field types

See storage format page for more information about how fields are stored in database.


Live text

These fields are visible in the Detail section of the issue view.

They are used to store text. It's the most common field type that suits most use cases.

They always display a "live" template - their snapshot equivalent is the Snapshot text field.

If you want to manipulate the value stored in a Live text field in a Script, you must use the Java API.

If you want to learn more about storage format in the dedicated storage format page.

Live user

These fields are displayed in the User section of the issue view.

They behave exactly like a regular Jira User field - they can be used:

  • in permissions schemes
  • as recipient of notifications in notification schemes
  • etc...

They always display a "live" template - they don't have a Snapshot equivalent.

Only active Jira users can be selected in an Elements Connect Live User field

Related troubleshooting articles:

Live text (legacy)

This field type was the standard field type before Elements Connect 5.9 where the compatibility with Jira Service Management has been added.

It will never be removed but we discourage the usage of this field type for new configurations.

If you have "Live text (legacy)" fields configured, you can keep using them.


Snapshot text

  • displayed in the Detail section of the issue view
  • store values in a text format
  • can only store a single value
  • can be used in JQL search like any standard text field (using ~ and !~ operators)

You can manipulate the value of these fields in a scripts the same way you'd do it with a regular text field

Snapshot date

  • displayed in the Date section of the issue view
  • store dates (without time)
  • can only store a single value
  • can be used in JQL search like any standard date field

Snapshot datetime

  • displayed in the Date section of the issue view
  • store dates and time
  • can only store a single value
  • can be used in JQL search like any standard date field