Improving Forge permission checks for Jira asApp requests
- Announced
- Tags
- forge-core-platform, forge-jira-cloud-platform, forge-jsm-cloud, forge-jsw-cloud
- Severity
- info, set by
reef/atlassian-rule-v2 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3445
What's changing We are updating how Forge permission checks are implemented in Jira for asApp requests. This internal change simplifies the evaluation process and removes the requirement for permissions to be synced to Jira at installation time.
This update improves the app installation process by reducing the overhead associated with permission synchronization.
What you need to do No action is required from you. This is an internal implementation change that does not affect how you declare permissions or use asApp in your Forge apps.
The update is being rolled out progressively on a tenant-by-tenant basis.
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.