Description:
Currently, when using Trigger for Jira events (such as avi:jira:created:issue), the expression filter only supports static checks based on the event payload. This severely limits the usefulness of Jira expressions for event filtering, as it is not possible to:

• Access entity properties (e.g., project or issue entity properties) unless they are already present in the event payload.

• Load additional context (such as project-level configuration or entity properties) during the evaluation of the expression.

Use Case:
A Forge app needs to preconfigure issue entity properties based on project-level rules, which are stored as project entity properties. Ideally, we would use a Jira expression in the trigger filter to check if relevant project entity properties exist and only invoke our function if necessary. However, due to the current restrictions, the function is invoked for every issue creation event, even when no action is needed, leading to unnecessary invocations and increased quota usage.

Request:
Please enhance Jira expressions in Forge triggers to support:

• Loading additional context (such as project, issue, or user objects) as needed for expression evaluation.

• Accessing entity properties (including project and issue entity properties) within the expression, even if they are not present in the event payload.