Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This article describes how to use placeholders in combination with SQL to specify a data source for a grid.  Table Grid Next Generation supports placeholders to query Jira values.

Excerpt
hiddentrue
Get data from Jira objects and use them to populate the grid.

Jira values can be used to populate the grid with data from Jira objects.

You can query the values from the following Jira-specific objects: issue, project, component, user and custom fields.

For example, you can populate the grid column with a default value retrieved from Jira object. 


You can use Jira values to populate the grid with data in different cases:

  • initialize grid with data 
  • set default values for gird columns
  • populate select lists with dynamic options retrieved from Jira
  • use custom field values in a grid: get data from a custom field which has a list of values and populate a grid with these values.

Supported values

Basic Jira Values

Issue Level specificProject Level specificCurrent User Level specific
  • issue/parent
:

    • id
    • key
    • summary
    • environment
    • estimate
    • logged
    • description
    • created_date
    • resolution_date
    • updated_date
    • due_date
    • votes
    • watches
    • security_level
  • status
:
    • id
    • name (default)
    • description
    • sequence
  • status_category
:
    • id
    • name (default)
    • key
    • sequence
  • resolution
:
    • id
    • name (default)
    • description
    • sequence
  • priority
:
    • id
    • name (default)
    • description
    • sequence
  • type
:
    • id
    • name (default)
    • description
    • sequence
  • assignee
:
    • id
    • key
    • name (default)
    • full_name
    • email
    • email_domain
  • reporter
:
    • id
    • key
    • name (default)
    • full_name
    • email
    • email_domain
issue:
  • components
      • id
      • name (default)
      • description
issue:
  • fix_versions
    • id
    • name (default)
    • description
issue:
  • affected_versions
    • id
    • name (default)
    • description
issue:
  • labels
    • id
    • name (default)
issue:
  • attachments
    • id
    • name (default)
    • file_size
  • project
    • id
    • key
    • name
    • url
    • description
  • category
    • id
    • name (default)
    • description
  • lead
:
    • id
    • key
    • name (default)
    • full_name
    • email
    • email_domain
  • components
      • id
      • name (default)
      • description
      • lead_name
  • versions
    • id
    • name (default)
    • description
    • is_archived
    • is_released
    • release_date
    • start_date
  • current_user
:

    • id
    • key
    • name (default)
    • ull_name
    • email
    • email_domain


Example placeholders for basic Jira values

Below you can find some example of the placeholders with the queries


Code Block
select name,price from sandwich_menu where restaurant={customfield:10010}


Custom Field Values

Single Value types

  • Date (should be treated as dates in our date column types)
    • Date Picker
    • Date Time Picker
  • Numeric (should be treated as dates in our date column types)
    • Number Field
  • All other custom fields without a specific type should be handled the same way - get custom field value as a string

Multi-Value types

  • Checkboxes
  • Labels
  • Radio Buttons
  • Select List (cascading)
  • Select List (multiple choices)
  • Group Picker (multiple groups)
  • User Picker (multiple users)
  • Version Picker (multiple versions)



Example placeholders for custom field values


Code Block
customfield:{id}


Code Block
titleexample
customfield:12345 // retreives data from the custom field with id
12345

This placeholder will take a Custom Field value for Single Value types, and merge values into one separated by a comma for Multi-Value types

Code Blockcustomfield:{id}:{'all' or the index of the value(all - is default value)}:{'name' or 'value'(name
 
- is default)}
  • customfield:12345:all:value
  • customfield:
    12345
    :all:name - will be treated like simple customfield:12345 since 'all' and 'name' are defaults
  • customfield:12345:1:value
  • customfield:12345:1:name - might be simple customfield:12345:1 since 'name' is a default
  • Selecting 'all' will merge values into one separated by a comma