Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Issue Panel Display Condition Not Working with customerRequest.requestType.id in Jira Expressions

Issue Panel Display Condition Not Working with customerRequest.requestType.id in Jira Expressions

phat_tran
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 16, 2025

Hi everyone,

I'm currently migrating my Jira Cloud app from Connect (using

ira:webPanels, in the atl.jira.view.issue.right.context location) to Forge (using the jira:issuePanel module)

In the Connect version, the issue panel displayed correctly using a Jira Expression in the conditions to check the customer request type, like:

YAML
conditions:
  - condition: jira_expression
    params:
      expression: project.properties?.['propertyKey']?.childKey?.includes(`${customerRequest.requestType.id}`)

This worked great in JSM projects to show the panel only for specific request types.

After migrating to Forge, the exact same expression (project.properties?.['propertyKey']?.childKey?.includes(`${customerRequest.requestType.id}`) doesn't seem to work — the panel is always hidden.

I've also tried safe navigation variations like:

  • project.properties?.['propertyKey']?.childKey?.includes(`${customerRequest.requestType.id}`)
  • project.properties?.['propertyKey']?.childKey?.includes(`${issue?.customerRequest.requestType.id}`)

But no luck so far.

Additional confirmation: When I hard-code the expression with a known valid request type ID (one that I retrieved directly via the Jira REST API), the display condition works perfectly and the panel shows as expected. This confirms that the property in my project do have valid customerRequest.requestType.id values populated.

  • project.properties?.['propertyKey']?.childKey?.includes(`HARD_CODE_VALUE`)


According to the Jira expressions type reference and Issue view conditions, the customerRequest context variable has a requestType property with an id, so it should be available.

Has anyone run into this during a Connect-to-Forge migration? Is customerRequest fully supported in Forge display conditions for issue panels in JSM issues? Any known differences, limitations, or workarounds (e.g., fetching via API instead)?

Documentation pointers or working examples would be hugely helpful!

Thanks a lot! 🚀

1 answer

0 votes
Thanh Le
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 16, 2025

come on

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events