We are at Atlassian Summit - which will affect our response times. Meet us there (if you happen to be in San Jose)

Skip to end of metadata
Go to start of metadata

The table grid editor documentation has moved to Table Grid Editor for Jira Server Documentation.


Overview Table Grid Editor Table Grid Reader Multi Level Cascade Still working on multiple issue trackers ? Synchronize any data flexibly with exalate


 

Introduction

The datasource specifications allow to specify how grids should be connected to databases. By separating out these connection details it is possible to

  • Stage grid configurations from a test environment to a production environment
  • Hide the password allowing to access the database
  • Reuse a connection in multiple grids

 

Managing data source specifications

Accessing the function

The data source administration pages can be found under the table grid add-on configuration pages.

JIRA VersionLocation of the table grid addon configuration pages
5.xAdministration -> Plugins -> Table Grid Editor -> Data Sources admin
6.xGear box in the top bar -> Add Ons -> Table Grid Editor -> Data Sources admin

 

Creating / modifying / deleting

 

On the data sources admin form, all the defined data source specifications are listed

Adding a data source specification

When adding a data source specification, you can select one of the supported databases.  Depending on this choice
different parameters can be provided.  Check with your database administrator in case of doubt. 

type = MySQLtype = Postgresstype = Oracletype = MS SQLtype = SYBASE

  • Password will never be shown on the screen
  • The id of the data source specification must be unique, and should only contain ascii characters (excluding punctuation, white space and so on)

Testing the connection

Use the test connection function to check if the configuration is correct.  
 

  • There is no explicit indication that the connection fails due to authentication errors (such as wrong password or userid)
  • The test connection is not validating that the user has the appropriate rights (create table, read / write)

 

Modifying a connection

 

  • When modifying a connection, you will not be able to change its id.
  • The password will only be updated if a new password is entered. 

Deleting a connection

  • There is no check if a datasource specification is being referenced from grid configurations.
    If a specification, which is in use, the referencing grid(s) will show a connection error the next time they are being used. 

 

Using the data source specifications in the grid configuration

The data source specification can be used in following properties

  • gd.ds
    This property specifies where the grid content must be stored.
  • gd.query.ds 
    This property specifies where the grid content must run the gd.query.
  • col.xyz.query.ds
    This property specifies where the content of a dynamic list should be retrieved.

 

Some additional notes 

  • Inner specifications are data source specifications which are defined in the grid configuration using the datasource.names
    and ds.xyz.connection properties as detailed on the database details - inner specifications page.
  • Admin specifications are data source specifications which are defined in the data sources admin forms.
  • When an admin specification has the same id as an inner specification, the inner specification will have priority
  • gridds is the default name where tables are stored when no gd.ds is specified.  An admin specification with the name 'gridds'
    will not be used.
  • jira is a reserved name.
  • You can change datasource configuration directly in the Jira database: the configuration is stored in the database table called AO_272C37_DSSENTRY 

 

Internal Java drivers to manage Data Source connections


type = MySQLtype = Postgresstype = Oracletype = MS SQLtype = SYBASE
version5.1.1642.1.4ojdbc7-12.1.0jtds-1.2.4