Forge display conditions now support arrays under logical operators for Jira and JSM modules
- Announced
- Tags
- adopting-forge-from-connect, forge-jira-cloud-platform, forge-jsm-cloud
- Severity
- notable, set by
reef/atlassian-rule-v2 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3510
What's changing Forge display conditions for Jira and Jira Service Management (JSM) modules now support arrays under the and, or, and not logical operators.
Previously, manifest keys had to be unique at each level, which made it difficult to repeat the same condition type or group multiple logical expressions. With this update, you can use an array of condition objects to define complex visibility logic more easily.
For example, you can now structure your manifest to group conditions or repeat the same condition type:
displayConditions:
or:
- and:
- entityPropertyExists: { entity: user, propertyKey: a }
- entityPropertyExists: { entity: user, propertyKey: b }
- and:
- entityPropertyExists: { entity: user, propertyKey: c }
- entityPropertyExists: { entity: user, propertyKey: d }
What you need to do No action is required for existing apps, as the previous syntax remains supported. If you want to simplify complex logic or repeat conditions in your Jira or JSM modules, you can update your manifest to use the new array-based syntax.
For more details and examples, see the Forge display conditions documentation.
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.