Page Comparison

...

Warning

Changing the value of the gd.tablename property has to be done with caution! Once the name is changed the grid starts using the new database table with new name for data storage and retrieval. The new data will be stored and there will be no problems with the new JIRA issues. But all the rows which you have added to the grid before the change of the name will be 'lost'. The data will still be in the 'old' table with the 'old' name, but the data will not be visible in the existing issues because once you have changed the gd.tablename the grid started working with the new table.

Class

Grid

Property

gd.tablename

Formal specification

gd.tablename = <basename of the table>

Required

no

Default

yes

Version

1.5

Comment

If no tablename is given, no table will be created in the database and the griddata will not be persisted.
- Data is stored in an in-memory database, which gets purged when JIRA is restarted or the plugin reenabled.
if a table name is given, either the gridds datasource must be available and configured, or a gd.ds property is specified
From v1.3 onwards, you can also specify gd.ds=jira to store the gridtable in the same database as used by JIRA.
From v1.12 onwards, gd.ds can reference one of the data source specifications.
the resulting table name will be a combination of the base name of the grid table and an id of the context obtained via Jira API.
the property gd.tablename replaces the now deprecated gd.table property.
the name of the table should not contain whitespaces.

Example

Code Block
gd.tablename=familylist

Reference

datasource.names
gd.ds
Datasource Specifications

Versions Compared

Old Version 4

New Version Current

Key