Forge Trigger avi:jira:updated:issue stopped firing since April 20th despite matching filter conditions

Forge Forge Modules and Product Triggers
1

Hi everyone,

I have a Forge app that transfers issues from a Service project to a Dev project. It uses the avi:jira:updated:issue event to trigger when an issue’s status is changed to “Waiting for Development”.

The app had been working perfectly fine for a long time, but it completely stopped triggering around April 20th. We haven’t made any changes to the codebase or the manifest.yml file.

Here is the trigger definition from my manifest.yml:

YAML

  trigger:
    - key: ud-forwarded-to-dev-trigger
      function: main
      events:
        - avi:jira:updated:issue
      filter:
        ignoreSelf: false
        expression: >
          event.changelog.items
            .filter(i => i.field == "status" && i.to == "10319") 
            .length > 0 &&
          event.issue.fields.issuetype.id == "10030" &&
          event.issue.fields.project.key == "UD"

To debug, I fetched the JSON payload of an issue that recently transitioned to this status via the Jira REST API (/rest/api/2/issue/UD-2276). The JSON confirms that my IDs are still perfectly valid and haven’t changed:

  • project.key is exactly "UD"

  • issuetype.id is exactly "10030"

  • status.id is exactly "10319"

Looking at the logs (forge logs), the function is not being invoked at all, which means it’s failing at the manifest filter evaluation step.

My questions are:

  1. Was there a recent platform change or bug regarding the avi:jira:updated:issue event payload around April 20th?

  2. Did the schema for event.changelog.items change? For example, is i.field maybe returning "Status" (capitalized) instead of "status", or has the i.to type changed?

  3. Is there any known outage with Forge triggers evaluating changelog items?

Any help or guidance on how to fix this would be greatly appreciated!

Thanks in advance.