Action Required: Update your Apps to comply with Jira Cloud Burst API rate limits

Jira Development Jira Cloud
,
21

I have two questions about your statement:

1) Forge Documentation - You say that Forge documentation “consistently” models REST API calls as backend responsibilities. And yet, the Forge CLI automatically provisions an Agents.md file with the following guidance:

When calling product APIs, it is often simpler to make API requests on the frontend using requestJira, requestConfluence, etc from the @forge/bridge package, rather than using a resolver on the backend.

That seems like an inconsistency. Is this guidance in Agents.md incorrect?

Internal Guidance – What is “internal guidance”? If it’s internal to Atlassian, does that mean we (external developers) don’t have access to it? And if so, how is it relevant?

4 Likes
22

Hey all, appreciate the feedback. You’re right that the earlier guidance to rely on backend resolvers adds unnecessary complexity for this use case. We’re working with our internal teams to determine how to surface the headers in Forge UI, without requiring any workarounds from you and will keep you updated on our progress.

2 Likes
23

They just introduced this: https://developer.atlassian.com/cloud/jira/platform/changelog/#CHANGE-3045

Should be live in 24h-48h according to this post 2026 point-based rate limits - #137 by MaheshPopudesi