FAQ
- svitlana (Deactivated)
Owned by svitlana (Deactivated)
Frequently asked questions on the usage and configuration of the Table Grid Editor
Troubleshooting
-
Changes are not logged in the activity and history section — Activity tab is not displaying grid changes.
We would need a place where it displays that something has been changed/edited.
-
Is it possible to initialize the grid with external data from custom fields? — You can initialize the grid data from the custom field. Even if it's We have been using the database custom field of Keppler with success.
-
Required field validation error is not displaying — I have a new TGE field, marked as a required field in the field configuration. It is displaying as a red asterisk (*) on the create Screen, but it doesn't work as expected. Whenever there is no row in the TGE field, there should be a failure message. The issue creates without a value for the TGE field.
-
Table grid has problems displaying more than 32,767 characters in edit mode — The entered text is too long. It exceeds the allowed limit of 32,767 characters.
-
The grid has problems connecting to the database — You have specified the datasource for the grid, but it does not connect to the database and you get an error message: "Could not connect to database jdbc: "
-
Unicode data is corrupted in text area column with PostgreSQL — I use PostgreSQL as a storage for JIRA data. Everything works fine except the case, when I try to enter any Unicode text (any national alphabet's characters) to the textarea column of my Grid - characters get corrupted.
Logging
-
How to disable excessive hibernate logging — When debug logging is enabled, all queries sent to the database will also be logged. I don't need excessive hibernate logging. How could it be disabled?
-
How to enable debug logging permanently — In the cases where you need to have a closer look at what the table grid editor is executing in the background, you can enable logging as described in this article.
-
-
How to enable temporarily debug logging — In the cases where you need to have a closer look at what the table grid editor is executing in the background, you can enable logging temporarily
-
Send us data about your support case — How to send us data to debug and/or reproduce your issues
Scripting and automation
-
Access the grid data using REST — As a developer, I want to access the grid information through a REST call
-
Bob Swift's "Create on Transition" integration — Bob Swift "Create on Transition" integration
-
Check if all actions have status 'Done' — Assume you track actions with a grid, and you want to validate that all rows in a grid have status 'Done'.
-
Copy the grid content to another grid — It is possible to do with TGE Java API and the ScriptRunner add-on
-
How to ensure that the grid has been modified when creating an issue — The required attribute of the custom field configuration has no effect on the behaviour of the grid. This faq details out how you can test if the grid has been modified when creating an issue
-
-
Use groovy script to transform a grid into subtasks — Use the table grid editor to create a list of subtasks
-
Using scripted fields to extract information from the grid (old) — Using a simple script, you can retrieve the values from the grid table and reuse these values in JQL and so on.
-
Using scripted fields to extract information from the grid using the table grid API — Using a simple script, you can retrieve the values from the grid table and reuse these values in JQL and so on.
-
Validate grid data on transition — Perform any custom checks of grid data on the issue transition screen