Troubleshooting & FAQ

This page provides answers for frequently asked questions on the usage and configuration using Table Grid Next Generation for Jira Server / Datacenter.

This can allow you to find solutions to your questions or problems and avoid to create a support issues for classic / known problems.


What is the difference between the Table Grid Next Generation and Table Grid Editor for Jira Server?

This is a completely new, improved version of the Table Grid Editor.

Following features are completely new in the Table Grid Next Generation:

  • Brand new look and feel, with the intuitive configuration interface

  • Service Desk Customer Portal support

  • Rich Data and Time formats

  • JavaScript formulas

  • Web service data sources support

  • Possibility to make the grid a required field

Check the feature comparison page for more details.

Do you provide migration from the Table Grid Editor for Jira Server to the Table Grid Next Generation?

We propose a migration program with a table grid migration tool and a path to convert your active TGE license to a TGNG license at no cost. If you are interested in the license migration, please submit a support request with all the requested details.

What Jira versions are supported ?

Table Grid Next Generation supports Jira starting from 7.4 version and higher.

How long would you support Table Grid Editor?

We plan to support the Table Grid Editor for Jira Server at least 1 year after the Table Grid Next Generation is feature complete - such that all table grid editor for server users can use the table grid next generation and have sufficient time to migrate to the new environment

Is the Table Grid Next Generation 100% backward compatible with the existing Table Grid Editor for Jira Server?

The Table Grid Next Generation is an alternative addon that overlaps the functionality of the Table Grid Editor for more than 80%. 

Is the grid Java API backward compatible?

(we do a lot of grid manipulation from groovy scripts)

TGNG has its own Java API and REST API

How to migrate TGNG Server/Datacenter to TGNG Cloud?

Here is the full documentation about how to migrate TGNG Server/Datacenter to TGNG Cloud.


Problems saving grid after the data import


Grid stores data in a textfield column of the customfieldvalue table in the jira database. Jira has a limit of 32767 characters set for the text field by default .


  1. Navigate to the Administration - Advanced Settings in your JIRA.

  2. Change the value of jira.text.field.character.limit property to 0.

  3. Update the configuration.

Grid value is not saving


In some cases, the last edited value in the grid is not saving due to the complex bug and our team is working on its fix. However, this process is time-consuming since it requires a rewrite of the component used to bring up the grid. 


  1. Change the grid value.

  2. Unfocus the grid cell by clicking in any place outside the grid.

  3. Save the grid by clicking on the checkbox in the left-down corner.

Grids always show up on customer portals even if they do not contain any data


Grid custom field presence is configured in the request types. The grid does not necessarily need to contain data, by default empty custom fields also show up.


If the empty grid takes too much space you can enable automatic grid size in the Grid Configuration → General Settings. This way the grid height will be limited to the number of rows. The empty grid will only contain one row with the column names.

Single Select List and Multi Select List static options disappear when I import my configuration

There is a dedicated page for about this problem:

The grid value is not saving without unfocusing the cell

Sometimes, when editing Table Grid values on the issue view, the changes can't be seen after saving the grid.


This problem happens if you input the value and save the grid right away, without unfocusing the cell. In this case, the grid does not pick up the most recent changes.



To resolve the issue we recommend using the following scenario when editing the existing grid configuration:

  1. Click the Edit icon to modify the grid on the issue view or double-click the cell you want to edit:


  2. Input a new value into a cell 

  3. Click outside the cell

  4. Save the Grid

Blank page when trying to add or edit value on grid configuration page

Sometimes, when editing grid configuration by adding values to the existing cells, the page goes blank and the changes do not apply.


This problem occurs when you enter new values in the existing grid configuration and unfocused the cell.



To resolve this we recommend using the following scenario when editing grid configuration:

  1. Click the Grids tab under the Table Grid menu and select the grid you want to edit 

  2. Click the Edit icon to open grid configuration page

  3. Input a new value in the grid cell and press EnterThis way the issue will not happen again when un-focusing the cell. You can make further changes and save the grid.


Table grid value does not persist on a failed transition validation

When a Table Grid field is present on a transition screen, any or changes made by the user are cleared in the validation for this transition fails.


This issue happens because Jira fires the "dialogReady" event and "editModeAction" is loaded which gets Grid Data from the back-end when the transition screen is loaded originally. Since this does not happen after a failed validation, the intermittent data is lost.



Since the issue is related to core Jira functionality, a complete solution is not available. As a workaround, we recommend placing Grid fields on transition screens that do not have frequently failing validators and/or adding warnings for users.

A "Grid has changed" entry is added to the Jira DB even when the grid was not changed


The problem appears when the issue is edited through "Edit Issue" mode in the pop-up. Due to the way TGNG interacts with and renders on Jira transition screens a 'customfield payload' is created when such a screen is open. This leads to Jira registering a change in the TGNG field even in cases where no values were altered. 



Due to the core nature of the issue, no direct solution is available.

Response to Log4j vulnerability - CVE-2021-44228

There is a dedicated page for about this problem:


Didn't find a feature you need? Suggest an improvement.