Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

This page includes answers to commonly asked questions related to the Table Grid Next Generation.


 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.


 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


 What Jira versions are supported ?

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


 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


 Problems saving grid after the data import

Reason

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 .

Workaround

  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

Reason

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. 

Meanwhile, please use the following workaround:

  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

Reason

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.

Workaround

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.

  • No labels