Data storage in Table Grid Cloud
We use Atlassian Connect Framework to integrate Table Grid Editor with Jira Cloud. The Table Grid is a web application that operates remotely over HTTP. It appears as a fully integrated part of Jira Cloud.
The Table Grid Editor for Jira Cloud (TGC) stores all the grid data in Jira Entity Properties on issue level. You can use Jira Cloud API to retrieve data from the grid.
Entity properties are key-value stores attached to Jira objects, which can be created, updated, and deleted via the Jira REST APIs. This is a powerful system for storing data on the Jira host; it supports imports, exports, and migrations between instances because the data is stored locally with the Jira Cloud tenant.
Every grid has its own entity property with grid data. Therefore, even when the grid has been removed or disabled, you can access the data from the entity property. For more details, please check storing data without a database on Jira Cloud. We store the grid configuration data on our own server.
How to get data from the entity property
Get a list of issue properties. How to get a list of issue properties on Jira Cloud.
Use the grid data key to get the data from the grid. How to get issue property using issue property key.
Example
Get issue property keys
To get the list of available properties you can use the following URL, where jira-instance1.net is your Cloud Jira instance URL
https://jira-instance1.net/rest/api/2/issue/10123/properties
Example response
{
"keys": [
{
"self": "https://jira-instance1.net/rest/api/2/issue/10123/properties/5a674fcf729257db93fc1187",
"key": "5a674fcf729257db93fc1187"
},
{
"self": "https://jira-instance1.net/rest/api/2/issue/10123/properties/5ad73a38dcc78f393cb0903b",
"key": "5ad73a38dcc78f393cb0903b"
},
{
"self": "https://jira-instance1.net/rest/api/2/issue/10123/properties/ducket-data",
"key": "ducket-data"
}
]
}
Get issue property
To get the value of the property with the given key you should use a key, received in previous step.
A key received as a response in the previous step
"key": "5a674fcf729257db93fc1187"
Example response