Why does the issue assigned trigger double the event volume?

Forge Forge Modules and Product Triggers
, ,
1

I just noticed that the documentation for the issue assigned trigger (avi:jira:assigned:issue) mentions that:

An “issue updated” event will also be sent when this occurs.

Based on my own testing, I can confirm that this is indeed the case. Apart from the eventType property, the event payloads of these two events are exactly the same.

Given the above observation, I thought I could remove the avi:jira:assigned:issue subscription and only receive avi:jira:updated:issue events. Unfortunately, that’s not the case. Removing the avi:jira:assigned:issue subscription means we no longer receive avi:jira:updated:issue events for issue assignments.

Why can we not receive either an issue assignment event OR an issue-update event? The current solution artificially doubles the event volume for no apparent reason.

1 Like
2

Below is a workaround to filter out the event duplicates. But in my opinion, the behavior when declaring both the issue updated and assigned events is faulty.

 trigger:
    - key: t-issue-updated
      endpoint: ep-t-issue-updated
      events:
        - avi:jira:updated:issue
        - avi:jira:assigned:issue
      filter:
        expression: "event.eventType != 'avi:jira:assigned:issue'"