Data Sources

Choose what data your panel displays: issues linked by link types, or issues found by a JQL query.

Data Source Types

Type Shows Table Use Case
Linked Issues Yes Display issues connected by link types
JQL Query Yes Display issues from any JQL search
None (don’t show linked issues) No Only the name, description and display fields (default)

Linked Issues

Display issues connected via Jira link types.

Configuration

  1. Select Linked Issues as data source
  2. Choose link types with direction:
    • Inward: “is blocked by”, “is cloned by”
    • Outward: “blocks”, “clones”
  3. Select table fields (columns to display)
  4. Optionally select display fields (fields shown above table)
  5. Configure pagination and limits

Each link type has two directions:

Direction Example Description
Inward “is blocked by” Current issue is the target
Outward “blocks” Current issue is the source

You can select multiple link types and directions. All matching linked issues are combined.

Example: Show Blockers

  • Link Type: “is blocked by” (inward)
  • Table Fields: Key, Summary, Status, Assignee
  • Max Issues: 50

This shows all issues that block the current issue.

Note: Select at least one link type in Link types for filtering. With none chosen the table shows no issues and the field is marked “No link type selected”.


JQL Query

Display issues matching any JQL search.

Basic Query

project = "Marketing" AND status = "In Progress"

Parametric Mode

Use template variables to create dynamic queries:

"Epic Link" = {{ issue.key }}
project = {{ issue.fields.project.key }} AND type = Bug

Available Variables in JQL

Variable Description
{{ issue.key }} Current issue key (e.g., PROJ-123)
{{ issue.id }} Current issue ID
{{ issue.fields.project.key }} Project key
{{ issue.fields.project.id }} Project ID
{{ issue.fields.assignee.accountId }} Assignee account ID
{{ issue.fields.reporter.accountId }} Reporter account ID
{{ currentUser.accountId }} Current user account ID

Shortcut syntax:

Shortcut Equivalent
{{ key }} {{ issue.key }}
{{ fields.project.key }} {{ issue.fields.project.key }}
{{ project.key }} {{ issue.fields.project.key }}
{{ assignee.accountId }} {{ issue.fields.assignee.accountId }}

Example: Epic Children

"Epic Link" = {{ issue.key }} ORDER BY status

Shows all stories/tasks in an epic, ordered by status.

Example: Same Assignee

assignee = {{ issue.fields.assignee.accountId }} AND status != Done

Shows other open issues assigned to the same person.

Example: Current User’s Issues

assignee = {{ currentUser.accountId }} AND status != Done ORDER BY priority DESC

Shows open issues assigned to the person viewing the panel.

JQL Validation

When configuring a JQL query, Display Linked Issues provides inline validation:

  • Syntax check - validates the JQL syntax before saving
  • Issue count preview - shows how many issues match the query
  • Error messages - displays Jira’s JQL error messages for invalid queries

For parametric JQL (using template variables), use the Test JQL feature in the Testing Panels page to verify the query resolves correctly with a real issue key.


Field Configuration

Two Types of Fields

The panel supports two different field selections:

Field Type Where Displayed Used For
Table Fields (linkedIssuesFieldId) Columns in issue table Linked Issues or JQL results
Display Fields (displayFieldIds) Above the table Current issue data

Table Fields

Choose which columns appear in the issue table.

Steps:

  1. Click Select Fields
  2. Check/uncheck fields
  3. Drag to reorder
  4. Click Save

Available Fields:

  • System: Key, Summary, Status, Priority, Assignee, Reporter, Created, Updated
  • Custom: Any custom fields in your instance
  • Form fields: Open forms, Submitted forms
  • Date fields: Due date, Start date, etc.

Default Fields: Key, Summary, Status, Priority, Assignee

Limit: Maximum 50 table fields per configuration.

Display Fields

Show current issue data above the table.

These are fields from the current issue (not the linked issues), displayed in a compact format above the table.

Use case: Show Epic name, Sprint, or other context when viewing linked issues.

Limit: Maximum 50 display fields per configuration.


Pagination and Limits

Max Issues vs Rows Per Page

Setting Purpose Range Default
Max Issues Total issues loaded from Jira API 1-1,000 50
Rows Per Page Issues displayed per page in table 1-100 10

How they work together:

  1. Max Issues controls how many issues are fetched from Jira - the JQL search pages through Jira results until it reaches this number (up to 1,000)
  2. Rows Per Page controls pagination display
  3. The panel shows paginated results up to Max Issues limit

Example:

  • Max Issues = 100, Rows Per Page = 10
  • Panel fetches up to 100 issues
  • Displays 10 per page with navigation
  • User can browse through 10 pages maximum

Note: The total shown by Show Count is Jira’s approximate count of all matching issues. It can be larger than Max Issues and is not the number of rows loaded into the panel.

Performance Recommendations

Scenario Max Issues Rows Per Page
Quick overview 25 5
Standard use 50 10
Comprehensive lists 200 25
Large datasets 1,000 50

Tip: Start with lower limits for better performance. Increase only if needed.


Template Variables

In descriptions, JQL queries and display conditions, you have access to these variables:

Issue Data

Variable Description
{{ issue.key }} Issue key (PROJ-123)
{{ issue.id }} Issue numeric ID
{{ issue.fields.summary }} Summary text
{{ issue.fields.description }} Description (may be ADF)
{{ issue.fields.status.name }} Status name
{{ issue.fields.priority.name }} Priority name
{{ issue.fields.assignee.displayName }} Assignee name
{{ issue.fields.reporter.displayName }} Reporter name
{{ issue.fields.project.name }} Project name
{{ issue.fields.project.key }} Project key
{{ issue.fields.issuetype.name }} Issue type
{{ issue.fields.created }} Created timestamp
{{ issue.fields.updated }} Updated timestamp
{{ issue.fields.duedate }} Due date

Shortcuts

See the canonical list of variable shortcuts in Templates → Issue Data.

Current User

See the canonical list of currentUser properties in Templates → Current User. {{ user }} is an alias for {{ currentUser }}.

Linked Issues (for Linked Issues/JQL sources)

Variable Description
{{ linkedIssues }} Array of all loaded issues
{{ linkedIssues.length }} Count of issues

Loop example:

{% for linked in linkedIssues %}
  {{ linked.key }}: {{ linked.fields.summary }}
{% empty %}
  No linked issues found.
{% endfor %}

Loop Variables

Variable Description
{{ loop.index }} 0-based index
{{ loop.index1 }} 1-based index
{{ loop.first }} True for first item
{{ loop.last }} True for last item
{{ loop.length }} Total items in loop

See Templates for complete syntax reference.


Custom Fields

Custom fields are accessed by their field ID (customfield_XXXXX). Access by field name is not supported - {{ issue.fields["Story Points"] }} resolves to nothing.

{{ issue.fields.customfield_10001 }}

Finding Field IDs

  1. In the configuration editor, open the Show issue JSON tab and click Download Issue Data
  2. Search for the field name in JSON
  3. Note the customfield_XXXXX ID

Common Custom Fields

{{ issue.fields.customfield_10001 }}          {# Story Points #}
{{ issue.fields.customfield_10002.value }}    {# Select field value #}
{{ issue.fields.customfield_10003 | date }}   {# Date field #}
{{ issue.fields.customfield_10014 }}          {# Epic Link - the ID differs per site #}

Next Steps