-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Forge - App UI Web
-
Minor
Issue Summary:
Unable to load a Jira Issue Type avatar image in a Forge app without specifying egress permissions for images: '*.atlassian.net' in the manifest, despite CHANGE-1978 stating this should not be required. When the egress is omitted, loading the avatar image fails with an egress permissions.
When the same url loaded in the custom UI project, it works fine.
Steps to Reproduce
- Create a UI KIT forge app.
- Remove the egress declaration for images: '*.atlassian.net' from the Forge app manifest.
- Attempt to display an Issue Type avatar image in the Forge app using the <Image> component and iconUrl.
- Observe that the image does not load, and an egress permission error is shown.
Expected Results
The avatar(both custom and default) should be rendered without any error similar to Custom UI project.
Actual Results
When the egress is omitted, loading the avatar image fails with an error:
Egress permissions for https://xxxxxxxx.atlassian.net/rest/api/3/universal_avatar/view/type/issuetype/avatar/10318?size=medium missing in the manifest.
Workaround
- The loading of images using hostname url works fine in the Custom UI project.
- Egress error can also be resolved by calling Jira Cloud platform REST API using asApp() or asUser()