Hi everyone,
I'm currently migrating my Jira Cloud app from Connect (using
In the Connect version, the issue panel displayed correctly using a Jira Expression in the conditions to check the customer request type, like:
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! 🚀
come on
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.