logoBack to App page
Requirements and Test Management for Jira
Cloud Data Center
Documentation
FAQ
Release notes
Migration DC → Cloud
Migration DC → AGC
Requirements and Test Management for Jira
Cloud Data Center
Documentation
FAQ
Release notes
Migration DC → Cloud
Migration DC → AGC
Last updated Aug 22, 2026

Issue Panel

Panel Filter Result

This chapter provides information on how to configure Panel Filter Result panels in RTM.

Warning

Before you start, log in as a user with the Jira Project Administrators permissions.

Panel Filter Result is a contextual panel displayed on the Jira issue view. Unlike a regular saved Jira filter, Panel Filter Result builds its query relative to the issue you’re currently viewing - JQL template placeholders are substituted with values from that issue, such as its key, assignee, status, fix versions, or components. The panel answers the question “show me issues related to what I’m looking at right now” and presents the results as a table.

A Panel Filter Result panel appears only when an enabled configuration exists for the given combination of issue type and project.

You can find Panel Filter Result in Space settings > RTM Configuration > Issue Panel.

Panel Filter Result configuration page.
Panel Filter Result configuration page.

Creating a custom panel

Custom Panel Filter Result panels let you extend visibility beyond RTM’s predefined panels and tailor results to your team’s workflow.

Steps

To create a custom Panel Filter Result panel:

  1. Click Add panel to open the Issue Panel Configuration dialog.
  2. Fill in the fields:
Field Description
Panel Title Name of the panel visible on the issue view.
Issue Type Issue type in the selected project on which the panel will be displayed. The JQL can still reference issues from any other project on the instance.
JQL Filters Static JQL appended with AND - narrows results further (e.g. status = Open).
Placeholder conditions JQL template with placeholders - the dynamic part defining the relationship to the current issue. Supports standard JQL autocomplete.
Issue Panel Configuration dialog.
Issue Panel Configuration dialog.
  1. Click Save.

Result

The panel is added to the list and appears on issues of the selected type.

Tip

If you don’t see the added panel on the issue view:

  1. Open an issue.

  2. Click View app actions.

  3. Click Related issues.

    Add related issues to the view.
    Add related issues to the view.
Example

Goal: You want to see all bugs assigned to the same person as the Functional Requirement you’re currently viewing.

Fill in the fields as follows:

Field Value
Panel Title Bugs for this assignee
Issue Type Functional Requirement
JQL Filters issuetype = Bug
Placeholder conditions assignee = _ASSIGNEE_

The panel displays all bugs assigned to John. If you reassign the Requirement to someone else, the panel automatically updates to show that person’s bugs instead.

Example
Example
Warning

Removing a panel is irreversible.

Placeholders

A placeholder is a special token you write in the JQL field, such as _ISSUE_KEY_ or _ASSIGNEE_. When someone opens an issue, RTM automatically replaces each placeholder with the actual value from that issue before running the query. This means the panel always shows results relevant to the issue the user is currently looking at - without any manual filtering.

If a field has no value on the current issue (for example, no one is assigned), RTM replaces the placeholder with an IS EMPTY condition so the query still works.

Placeholder Replaced with If the field is empty
_ISSUE_KEY_ Issue key -
_ASSIGNEE_ Assignee assignee IS EMPTY
_REPORTER_ Reporter reporter IS EMPTY
_STATUS_ Status -
_RESOLUTION_ Resolution resolution IS EMPTY
_FIX_VERSION_ Fix version(s) fixVersion IS EMPTY
_AFFECTED_VERSION_ Affected version(s) affectedVersion IS EMPTY
_COMPONENT_ Component(s) component IS EMPTY
Tip

Use JQL for the part that connects the panel to the current issue - this is where placeholders go. Use Filter JQL for conditions that should always apply, regardless of which issue is open (e.g. status != Done, issuetype = Bug).