Storage format

 

Table of contents


With Elements Connect 6 the storage format for Elements Connect fields changed from XML (Elements Connect 5) to JSON. In this article we will introduce you to the new format, explain how it works and how to manipulate it.


Where the data is stored ?

No matter which version of Elements Connect you use, for user and text Elements Connect fields data are stored in the TEXTVALUE column of the CUSTOMFIELDVALUE table. For date and datetime Elements Connect fields, values are stored as timestamp in the DATEVALUE column of the CUSTOMFIELDVALUE table.

In a project, if you already retrieve the Elements Connect 5 (XML) value directly in your code, it will not be compatible with Elements Connect 6.


We do not recommend you to access data directly, use the Elements Connect APIs instead.



Elements Connect API

Elements Connect has a Java API and a REST API that allow you to manipulate fields. See the pages Java API or REST API for more details.



Storage format across versions

This table shows only storage format differences across Elements Connect versions. For more informations about Elements Connect fields look at the different field type page.




NameStorage format (Elements Connect 5)Storage format (Elements Connect 6)

Live Text

CHANGED

Single value

<content>
	<value>KEY</value>
</content>

Multi value

<content>
	<value>KEY-1</value>
	<value>KEY-2</value>
	...
	<value>KEY-N</value>
</content>

Single value

{
    "keys":["KEY"]
}

Multi value

{
    "keys":[
		"KEY-1", "KEY-2", ..., "KEY-N"
	]
}

Live User

CHANGED

Single value

<content>
	<value>john.duff</value>
</content>

Multi values

<content>
	<value>john.duff</value>
	<value>john.doe</value>
	<value>john.leehooker</value>
</content>

Single value

The field key, as returned by the query

john.duff

Multi values

The field keys, as returned by the query, separated by \n.

john.duff\njohn.doe\njohn.leehooker

Live Text (Legacy)

CHANGED

Single value

<content>
	<value>KEY</value>
</content>

Multi value

<content>
	<value>KEY-1</value>
	<value>KEY-2</value>
	...
	<value>KEY-N</value>
</content>

Single value

{
    "keys":["KEY"]
}

Multi value

{
    "keys":[
		"KEY-1", "KEY-2", ..., "KEY-N"
	]
}

Snapshot Text

N/A

Not available in this version.
The value as seen in the issue

Snapshot Date

UNCHANGED

Value is stored as a Timestamp in the datevalue column of the customfieldvalue  table in Jira DB


Snapshot Datetime

UNCHANGED

Value is stored as a Timestamp in the datevalue column of the customfieldvalue  table in Jira DB