This page describes how you can use dynamic query on a database custom field in an issue.
Example 1
The following steps explain how to use a dynamic query to retrieve values for a database custom field, based on the values of other custom fields.
Log into your Jira as Admin.
Go to Administration > Add-ons > Database Custom Field and ensure that your dynamic sql is configured.
The database Product Name custom field depends on the Published(customfield_11900) and Not published(customfield_11901) custom fields.
Go to the issue and try to edit it. For this example, we used the same issue as on theUsing Autocompletepage.
So it looks like in the following picture on edit:
Let's change the values for the Published and Not published fields, that we created for this example. These fields have the following ids: customfield_11900(Published) and customfield_11901(Not published). These are simple Jira custom fields, of the "Text Field (< 255 characters)" type.
For the Published field, type "jjupin". When you leave the input textbox for the Published field, the values for Product Name and Product Id fields are dynamically changed to empty values, and the available list of values for the Product Name is updated. This will be visible when you try to enter a new value by using autocomplete.
Type a value for the Not published field, "databasecf" for instance.
Use autocomplete to see the values available for the main database custom field – Product Name.
The only option left is the one displayed, which is equal to the value of the Published field. On selection, the child database custom field is automatically filled in with the id of the selected product.
After we save the issue, the values for the custom fields are displayed in the view issue screen:
In a similar way, you can use a dynamic query to retrieve values for a database custom field in a select list.
Every database custom field has a default value: blank, displayed in a the field of the Select List type as "None".
Example 2
For the next example we used a configuration where parent fields depend on each other, and when one field changes, all of the dependent fields are changed as well.
This means that:
Product Name depends on Category and has Product Code
Version depends on Product Name and has Release Date.
If you change the Category field from "support" to "services", all values are changed.
Note that if the session expires, the autocomplete, or other requests will not be completed, but Jira can still update the issue if the password of the user is kept in memory.
The database custom field and its dependent database custom fields should all be on the same screen, context.