Table Grid Editor cannot add rows or read data after upgrading Jira from 9.x to 10.x+ When gd.tablename contains a dot

Problem

After upgrading Jira Data Center from 9.x to 10.x (or later), Table Grid Editor (TGE) fails to add new rows or read existing grid data when the gd.tablename property in the grid configuration contains a schema prefix with a dot (.).

For example, if the grid configuration uses:

gd.tablename=cashcollect.cc_fonds_demandes

The grid will appear empty and CRUD operations (add row, edit, delete) will no longer work.

Important: Your existing data is not lost. It remains in the actual data table in the public schema - TGE simply can no longer locate it after the upgrade. Applying the workaround below restores access to that data.

🔍 Reason

In Jira 9.x and earlier, TGE used an older version of the Hibernate ORM framework that tolerated table names containing a dot (.). Internally, Hibernate interpreted only the part after the dot as the actual table name and created/accessed the table in the public schema of the database. The schema prefix (e.g., cashcollect) was effectively ignored.

For example, with gd.tablename=cashcollect.cc_fonds_demandes, TGE actually stored and read data from a table named cc_fonds_demandes_c<fieldId> in the public schema — not in the cashcollect schema.

After upgrading to Jira 10.x, TGE uses a newer Hibernate version that no longer tolerates table names containing a dot. As a result, TGE can no longer locate or access the grid data, causing the grid to fail.

✅ Solution (Workaround)

Remove the schema name and the dot (.) from the gd.tablename property in your grid configuration.

You can find this property in the Table Grid Editor field configuration.

Before:

gd.tablename=cashcollect.cc_fonds_demandes

After:

gd.tablename=cc_fonds_demandes

After applying this change, TGE will correctly access the actual data table (e.g., cc_fonds_demandes_c<fieldId>) in the public schema, and all grid operations will work again.

Note: A permanent product fix is not possible because the newer Hibernate version used in TGE for Jira 10.x does not support table names containing a dot (.). This workaround is the recommended solution.