Grid reload

You can initialize the grid using the gd.query property. The query allows retrieving information from another database table so that values can be adapted dynamically. Grid reload functionality helps to update these values in the grid.

Example

Typically you can use this to list a set of default tasks to be executed when resolving an issue.

gd.columns=task, assignee, status
gd.query=select summary from defaultTasks

You can use gd.query.parameters(deprecated) or inline parameters method to initialize the grid with a query which depends on specific values of the containing issue.

For instance if you want to create a task list, based on the issue type.
In case of a bug, you need to investigate why the issue slipped through the testing, while for an improvement request you need to add a couple of test cases.

gd.columns=task, assignee, status
gd.query=select summary from defaultTasks where taskFor = {0}
gd.query.parameters = issue:type

The {0} will be replaced with the typename of the issue (Bug, Improvement, ...)

Alternatively, the grid can depend on a custom field.

Check out the Sandwich menu from different vendors : example pre-populate a table grid for an example where the user selects a vendor from a drop down box.

This will trigger a refresh of the grid taking into account the new value of the custom field(the one that stores vendors' list)

gd.query=select vendor,sandwichname,price from sandwichprices where vendor = {0}
gd.query.columns=vendor,sandwich,price
gd.query.parameters=customfield:10150
gd.query.ds=gridds

The grid query will reload again when the customfield is modified, after removing the existing rows according to the gd.query.keepOnRefresh setting.

Table Grid Editor (legacy) Documentation

Grid reload

Example

See also