Skip to end of banner
Go to start of banner

Configuration

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 55 Next »

Configuration

Configure the Power Database Fields plugin following the steps below:

     1. Log in as JIRA administrator. Go to the Administration->'Add-ons' menu, 'Manage add-ons' sub-menu. Make sure that both plugins katl-commons and Power Database Fields are enabled.

    

    2. From JIRA Administration Administration->'Issues' menu, 'Custom fields' sub-menu add the custom fields of the following types as needed:

  • 'Database Information' (database custom field);
  • 'Database Child Information' (child for a database custom field);
  • 'Data Table Information'


    

     At least one database custom field must be added(to have something to configure). Add as many Database Information or Database Child Information custom fields as you need.

    

    3. Access the 'Database Custom Field' configuration page from Administration->'Add-ons' menu, 'Database Custom Field' sub-menu:

    

    4. Configure the parameters for Database Custom Field

The first parameter to configure is the timeout(in seconds) for the cache of the configuration values. If no value is specified, the default value used is 300.

      For each main database custom field added at step 2, there is a set of parameters to configure in this page. For each entry (main database custom field) choose:

  • Type of Custom Field: Select list or Autocomplete. If Autocomplete is chosen, the values of the field appears depending on the letters typed in the field, on issue. If Select list is chosen, the values of the field appear in a combo box.
  • Multiple Values: If checked, you can select multiple values from the database for the given database custom field.
  • Add None Option (only for type select list): When type is select list you can choose to show 'None' option or not for each individual database custom field.
  • Accept Any Value (only for type autocomplete): When type is autocomplete and this flag is checked, you can enter free text in the dbcf field input, even if the relevant entry is not listed in the database
  • Sql Query: The sql query to be run, for instance SELECT col1, col2, col3, col4 FROM testTable. It can be either a simple sql, or a dynamic sql like in the above picture.

Oracle

If you use Oracle, the ";" character placed at the end of the query causes a SQL error. It complains about invalid character. Please remove it from the query.

  • Column: one of the columns selected by the sql query, for instance col1. This column will be used to get the values for this database custom field.

     If you want, you can configure the list of child database custom fields using the Add/Remove child buttons. The child fields are associated to the main database custom field. For each child, configure the following:

  • Child Custom Field (One of the child database custom fields added at step 2): These are visible for selection only when multiple values flag isn't checked for the parent database custom field.
  • Column: one of the columns selected by the sql query, for instance col2. This column will be used to get the value for this child (The value for the child is completed automatically after a value for the main database custom field is selected)

     Save the settings using the "Save configuration" button.

     5. Configure the parameters for Data Table Custom Field

     6. If everything is fine, in the Create or Edit page for an issue you should be able to see the values for the main database custom fields configured, and when selecting one of the values for a main database custom field, the children for the respective main database custom field will be automatically completed.

  • No labels