notableaddedAtlassian calls it: Added
Forge triggers now support entity property filtering and payload enrichment
- Announced
- APIs
- forge-jira-cloud-platform
- Severity
- notable, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3274
You can now use Jira entity properties (issue, project, and user) to filter Forge trigger events and include them in the delivered event payload. This allows your app to process only relevant changes and reduces unnecessary executions.
What’s changing
- Entity property filtering: You can now define expressions in your
manifest.ymlthat use Jira entity properties to filter events before they trigger your app. - Payload enrichment: Relevant entity properties can now be included directly in the event payload, eliminating the need for additional REST API calls to fetch this data.
What you need to do
- Update your
manifest.ymlto includeexpressionfilters using entity properties. - Update your event handlers to utilize the enriched payload data.
- For more information, see the Forge Trigger module reference.
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.