Display Conditions

Dynamic conditions that control when panels appear based on issue data, user context, or JQL queries.


Display JQL Condition

Dynamic filter using JQL. Panel shows only when the current issue matches this query.

How It Works

The system runs the JQL query with the current issue and checks if it returns a match. This is evaluated for each issue view.

Basic Examples

priority in (Highest, High)
status = "In Progress"
labels = "important"

With Template Variables

assignee = {{ currentUser.accountId }}

Shows panel only when current user is the assignee.

reporter = {{ currentUser.accountId }}

Shows panel only to the issue reporter.

project = {{ issue.fields.project.key }} AND type = Bug AND status != Done

Complex condition using issue context.

currentUser() vs {{ currentUser.accountId }}

Display JQL is regular Jira JQL, so Jira’s built-in currentUser() function works here:

assignee = currentUser()

In the data-source JQL templates (the JQL that loads issues for the panel) currentUser() does not work - that JQL is rendered through the template engine before being sent to Jira, and the function is not available. Use {{ currentUser.accountId }} instead:

assignee = {{ currentUser.accountId | jqlRaw }}
Where What to use
Display JQL (visibility condition) currentUser() or {{ currentUser.accountId }} - both work
Data-source JQL (loads issues) {{ currentUser.accountId }} only - currentUser() does not resolve

Combined Conditions

priority = High AND status != Done
duedate < now() AND status != Done
(priority = Highest OR labels = "urgent") AND status != Done

Display Condition (Template-Based)

Template-based filter for dynamic panel visibility. More flexible than Display JQL - supports complex logic.

How It Works

The expression is evaluated server-side, by the app’s template engine, before the panel content is returned to the browser. Nothing about the condition or the data it reads is sent to the client, and a user cannot bypass it from the browser.

The engine interprets the output:

Output Panel
Empty string, false, no, 0 Hidden
null, undefined, none Hidden
Any other value Shown

The comparison is done on the rendered text, so the strings "false", "no", "0", "null", "undefined" and "none" hide the panel just like the corresponding values.

Basic Examples

Check labels:

{{ 'urgent' in fields.labels }}

Check priority:

{{ fields.priority.name == 'High' }}

Check assignee exists:

{% if fields.assignee %}show{% endif %}

Check current user is assignee:

{{ fields.assignee.accountId == currentUser.accountId }}

Expression vs If-Statement Style

Expression style - outputs true/false:

{{ fields.priority.name in ['High', 'Highest'] }}

If-statement style - outputs text or nothing:

{% if fields.priority.name == 'High' %}show{% endif %}

Both styles work. Expression style is more concise for simple conditions.

Combined Conditions

AND logic:

{{ fields.priority.name == 'High' and fields.status.name != 'Done' }}

OR logic:

{{ 'urgent' in fields.labels or fields.priority.name == 'Highest' }}

Complex conditions:

{% if fields.priority.name in ['High', 'Highest'] and fields.assignee %}
  {% if fields.duedate and isPast(fields.duedate) %}show{% endif %}
{% endif %}

Display Condition vs Display JQL

Feature Display Condition Display JQL
Syntax Template expressions JQL query
Evaluated on Server-side, by the template engine Server-side, by a Jira JQL search
Complex logic Easy (and/or/if) Limited
Current user checks currentUser.accountId currentUser()
Performance Faster (evaluated on data already loaded) Slower (extra JQL search)
Error behavior Fail-close (hide) Fail-close (hide)

Both are server-side controls. Neither is evaluated in the browser, so neither can be defeated by editing the page.

When to use which: Use Display Condition for most cases. Use Display JQL when you need to check related issues or fields not available in issue data.


Error Handling

Both mechanisms fail closed: if the condition cannot be evaluated, the panel is hidden.

Display Condition (Fail-Close)

Display Condition uses fail-close behavior:

  • If expression has syntax errors → panel hidden
  • If required data is missing → panel hidden
  • If evaluation fails → panel hidden

This prevents accidental exposure of panels when conditions can’t be properly evaluated.

Display JQL (Fail-Close)

Display JQL also uses fail-close behavior:

  • If JQL has syntax errors → panel hidden
  • If the query fails → panel hidden

Always test your JQL conditions before deploying: a broken query makes the panel disappear everywhere, not appear everywhere.


Common JQL Patterns

By Status

status = "To Do"
status in ("In Progress", "In Review")
status != Done
statusCategory = "In Progress"

By Priority

priority = Highest
priority in (High, Highest)
priority != Low

By Dates

duedate < now()
duedate <= endOfDay()
created >= -7d
updated >= -1d
created >= startOfMonth()

By Labels

labels = "needs-review"
labels in ("urgent", "escalated")
labels is EMPTY

By Components

component = "Backend"
component in ("API", "Database")
component is EMPTY

By Custom Fields

"Team" = "Engineering"
cf[10001] = "Value"
"Story Points" > 5

By Current User

assignee = {{ currentUser.accountId }}
reporter = {{ currentUser.accountId }}
watcher = {{ currentUser.accountId }}

Troubleshooting

Panel Not Showing

  1. Test Display JQL in Issue Navigator - Add AND key = ISSUE-123 to test with specific issue
  2. Check Display Condition syntax - Use Preview to test template expressions
  3. Verify data exists - Check that fields you’re testing actually have values

Panel Showing Everywhere

You may have left the conditions empty - an empty Display JQL and an empty Display Condition place no restriction on visibility.

Panel Hidden Everywhere

A syntax error or an evaluation failure in either mechanism hides the panel: both Display JQL and Display Condition fail closed. Check the condition with Test Context and the JQL in the Issue Navigator.

Testing Display Conditions

Use the Preview Panel and Test Context features with a real issue key to test how your conditions evaluate. See Testing Panels for detailed instructions on testing display conditions.


Next Steps