We have a Forge app that displays dates on its app screen, and we want to render them according to the user’s Jira datetime format so they look consistent with the rest of the Jira UI.
As far as we can tell, the only way to read the instance-level datetime format is through the /rest/api/3/application-properties endpoint, which requires the read:instance-configuration:jira scope on Forge (equivalent to ADMIN for Connect apps).
The problem: adding this scope to an existing app triggers a major version bump and forces every admin to manually approve the new permission. Requiring an admin-level scope just to display dates in the user’s preferred format feels disproportionate, especially for a Forge app.
/rest/api/3/myself gives us the user’s locale and timeZone which we can combine with Intl.DateTimeFormat on the frontend to get a locale-appropriate format. But this only reflects the user’s locale, not any custom datetime format an admin may have configured in Jira’s advanced settings.
Questions:
- Is there any user-scoped or otherwise lighter-weight way to read the instance’s configured datetime format?
- If not, is there a recommended pattern for apps that want to respect the admin-configured datetime format without forcing a major-version permission upgrade on every install?
Any guidance or confirmation that admin scope is genuinely the only path would be appreciated.