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. 

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.

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.

Cause

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.

Solution

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.

Cause

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

Solution

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.

Cause

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.

Solution

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

Cause

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. 

Solution

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:

Error while creating issue

If this happen to your Table Grid, please follow one of these instructions:

Reason 1: Invalid Datasource

When connecting with an external datasource (REST, MySQL,…), make sure you hit Test connection button. If it shows Error pop-up message, you should review the datasource information again.

If it shows Success pop-up message, you will be able to create new issue with the grid.

Reason 2: Invalid Database table name

This issue happen when user delete database table name in external datasource REST, MySQL,… after connected it with a grid. Please make sure your table is existed in the database.

Here is a example of a successful database table name, successful pop-up message appears:

Solution

User can create an Atlassian Support Zip file following these instructions: https://confluence.atlassian.com/display/Support/Create+a+Support+Zip, go to atlassian-jira.loglogs and filter using the following bash command to see which grid configurations are wrong:

cat atlassian-jira.log | grep "Error creating issue" -A10 

Example of the results:

2024-02-29 07:59:03,419+0000 http-nio-8080-exec-295 url: /secure/QuickCreateIssue.jspa; user: admin ERROR admin 476x32161x2 1ebx2de 42.115.244.194,172.18.0.2 /secure/QuickCreateIssue.jspa [c.a.j.bc.issue.DefaultIssueService] Error creating issue: 
com.atlassian.jira.exception.CreateException: DBActionFailure(WrappedArray(ErrorPlaceholder(Error connecting to jdbc:mysql://htz-tablegrid02.exalate.systems:3317/tablegrid: Communications link failure

Java API doesn't work to get/read data of grid

With rows were added to grid using UI:

• The grid will show #error in wrong formula column (Picture 1) and return calculated value in other correct formula columns (Picture 2).

• With rows were added to grid using API (REST/Java API): When you put a wrong formula column, you can see the grid will return active (Picture 3) and return null if the formula is incorrect (Picture 4).

Customer can investigate more about the issue in tab “Logs”:

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