Sharing a new Forge bug we discovered this week as part of Connect to Forge conversion.
Problem: Using Forge auth tokens to call the JIRA Rest API asApp() returns all data localized to zh_CN, NOT the region of the Jira Site. This affects our apps because we need to pull certain localized values (e.g. issue status) for reporting.
Reference: Atlassian has published this new Forge bug as ECO-1480: [ECO-1480] Unexpected locale change in API Response when called asApp() in Forge - Create and track feature requests for Atlassian products. It is similar to bug ECO-674 which was fixed last year.
Workaround: Our hack workaround is to manually pull siteInfo from Jira to get the customer’s site locale, and then force override the accept-language headers in the REST API requests.
Note that the REST API localization works properly using a Connect JWT token, authenticating as the exact same app user account that Forge can’t do properly.