XIO

xWire

Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.

The Atlassian Developer Community - Latest posts

Latest posts

Forge UI Kit app never renders — issuePanel AND globalPage both stuck on skeleton, no iframe in DOM, empty forge logs

When the panel never gets an iframe, Jira usually failed on one of its own bootstrap calls before it asked for your app, so the answer is in the browser, not in forge logs. A HAR from a fresh load of the issue would show which request failed and with what status. I wrote a small local script that sorts a HAR’s failures by owner (network, Atlassian, app) and strips tokens first: GitHub - VovikP/har-triage: Sort a HAR file's failed and slow requests by who owns the fix: your network, Atlassian,…

RFC-157: Forge Workflows API

Thanks for the RFC. It’s very close to what we’d need to move our backend orchestration onto Forge. Context: we build a Confluence Cloud app that runs bulk archiving and clean-up jobs across whole sites. These jobs run on AWS Step Functions today. A parent job fans out over all spaces in a site, using child executions of up to 1,000 spaces each. Each space loops over its content in batches of 250, and a completion handler closes the job whatever its final status. We mapped this onto the…

CQL filter on data classification

Hi @MaricqJohan, nothing has changed since August. CONFCLOUD-84214 is still Gathering Interest with 35 votes and no Atlassian comment, and the CQL fields reference still has no classification field. If your Confidential pages sit in their own spaces, you can leave those spaces out in the connector’s content settings, which have an include/exclude spaces option separate from the CQL filter (deployment doc). For a custom pipeline only, GET /wiki/api/v2/pages/{id}/classification-level reads the…

Work Item View 2.0 for Ecosystem Partners

Hi everyone, Stepping in for Ahmud here as I’ve taken over this space! As we have started the General Availability (GA) rollout of the new Jira work item view, we wanted to share an important update regarding Issue Glance panels. The new work item view does not support legacy Issue Glance modules (which were deprecated back in Jira Cloud Platform changelog). If your app currently relies solely on an Issue Glance module, your panel will not render for users on the new view. To ensure your panels…

Is Canada a supported payout country for Marketplace Partners?

Adding Türkiye to this thread, as requested above, instead of opening a new topic. I’m an individual developer resident in Türkiye, with no registered company. I’m planning a Forge app for Jira Cloud, listed as Paid via Atlassian from the first release. The earlier Türkiye thread (102081) didn’t get an answer from the Marketplace team, so I’d like to confirm before I start building: Registration: Can an individual resident in Türkiye, without a registered company, register as a Marketplace…

Forge rovo:mcp: asUser tools always return MCP_UNAUTHENTICATED "User consent required"; consent does not persist

One workaround I’ve found for now is: Add a rovo:agent to your app and add those actions to the agent. Invoke those actions from the agent in a Rovo chat session That should create the auth successfully Now you MCP tool should work externally because the auth has already been established

requestTeamworkGraph works from a UI resolver but returns "User is not permitted to query this organization" inside a Rovo action

Hi @EbukaHenry, I tried re-creating this and jiraWorkItemLinkedExternalPullRequests query worked fine from my action module. I did see the “User is not permitted to query this organization” error once buy couldn’t recreate it again. Can you try re-deploying, creating a new chat session etc. and see if the error persists? If so please log a support ticket and we might be able to investigate further.

Forge rovo:mcp: asUser tools always return MCP_UNAUTHENTICATED "User consent required"; consent does not persist

Hey @TharunReddyKandukuri thanks for raising - I think you’ve found a bug here. The (internal) authentication fails in actions via MCP when your app has both jira and confluence scopes. I think your tools will work if you only have Jira or Confluence scopes - but I guess that breaks your use case. That auth URL being returned isn’t something that should be part of the flow. I’ll get the team to have a look.

Paid Marketplace app using the Forge LLMs API: eligibility, rate limits and data residency

Hi Ali, Forge LLM is GA and can be used by all apps (FYI Preview features can also be used by all apps). I’ll have a hunt through the docs to try and find that outdated preview reference. The limits are per installation. We’re constantly reviewing this as usage for Forge LLM scales up so reach out via a help ticket if you’re getting close to these limits. As of today, all LLM inference is in the US. At Team EU we announced that EU inference is coming soon, and as that rolls out for Rovo it will…

requestJira fails behind zscaler proxy

My work just recently implemented a zscaler proxy. I have been trying to work through a forge tunnel which mostly works, except for requestJira commands. They always fail with an “unable to get local issuer certificate” error, similar to Error: request to https://api.atlassian.com/graphql failed, reason: unable to get local issuer certificate However, specifying NODE_EXTRA_CA_CERTS does not work, in fact if I run the following code within my function, it lists all the “normal” CA certs and none…

PDF export fails ("Something went wrong") on pages with many Forge macros whose adfExport returns null for PDF

Update: Atlassian confirmed this is fixed as of 2 November 2026 (CONFCLOUD-85221), on all sites. The cause was iframe style injection that could stall indefinitely and block PDF generation; the fix caps the total wait and limits browser work on iframe-heavy pages. There is no release note, as it’s a backend change. Thanks to everyone who helped reproduce it.

Connect to Forge: Can the app’s domain change over time?

Hi @rmassaioli, Thanks for the suggestion! Unfortunately, that won’t work for us: the external service is called from our app’s frontend, so to get a fixed origin we would have to wrap the whole app in an iframe served from our own domain. That would effectively turn it into a kind of Connect inside Forge, which is exactly what we’re migrating away from. Could you share any comments on the original question? Even a short answer would help a lot, in particular: is the domain the same for all…

Connect to Forge: inScopeEUD versioning — analytics egress only?

Hi everyone, I’m having trouble understanding the versioning rules for inScopeEUD. The App versions page lists changing inScopeEUD from false to true “for the first time” as a major version trigger, and the In-scope End-User Data page explains that such a change is major if no other egress permission already has inScopeEUD: true, and minor otherwise. However, all the examples on the In-scope End-User Data page use entries with category: analytics, and in the sample forge version compare output…

Rovo Chat related links for connector documents don’t resolve via graph:smartLink

Hi everyone, We’re building a Forge app with a graph:connector that ingests atlassian:document objects into Teamwork Graph. Each document has a displayName and a url that points to our web app. Those URLs need a login, but they can be resolved via graph:smartLink, which works fine in another Forge Jira app we’re developing. In Rovo Chat, the sources of our documents are always resolved via the fallback public-object-provider instead, so they only show our page title and domain. We tried both…

RFC-157: Forge Workflows API

Thanks for the RFC! We have our own job system on top of async events, so we’ve built most of what you list under “Problem” ourselves. Parallel invocations per run and `waitForSignal()` look great. A few things from the draft docs would make it hard to move our bigger jobs over, though: ~1,000 pushes per run. Our larger jobs can get into that range, and retries and sleeps draw from the same budget. Splitting a job into several runs puts the tracking and joining back on us. Could the budget…

2 things that tripped me up shipping a Forge app in 2026 (a checklist for Connect → Forge movers)

With Connect end of support on 31 January 2027, a lot of us are moving apps to Forge right now. I just took a Forge app from zero to Marketplace submission: a Jira global page, a dashboard gadget, a Confluence macro, a Rovo agent and scheduled jobs. Here’s what actually cost me time. Hopefully it saves you some. Platform and tooling Pin your Forge CLI version. A CLI major version raised the minimum Node version mid-project and broke deploys on my machine. Put the CLI version in your README or…

Paid Marketplace app using the Forge LLMs API: eligibility, rate limits and data residency

Hi everyone, We’re preparing a paid Forge app for Jira Service Management. It uses the Forge LLMs API (llm module, @forge/llm, Claude Haiku) to classify requests and help agents translate and draft replies. It has no remotes and no egress, and forge deploy reports it as eligible for Runs on Atlassian. Before we submit, we’d like to confirm three things: Paid listings: may a paid-via-Atlassian Marketplace app use the Forge LLMs API today? Some earlier pages called the API “Preview”, and we…

Forge rovo:mcp: asUser tools always return MCP_UNAUTHENTICATED "User consent required"; consent does not persist

Our Forge app exposes 6 tools through the rovo:mcp module. An external MCP client (official MCP Python SDK, OAuth 2.1 to mcp.atlassian.com/forge/<appId>) connects and lists all 6 tools, but no tool call ever runs. Setup App ID f753cecd-d0ad-48d6-a7a0-58834ff31188, production environment, Forge CLI 15.1.0 Installed in Jira and Confluence on the same site; “Expose tools to MCP-compatible apps” enabled on both installations All tools call product APIs with api.asUser() Admin user tools/call any…

requestTeamworkGraph works from a UI resolver but returns "User is not permitted to query this organization" inside a Rovo action

Hi. I’m building a Codegeist 2026 entry. A Teamwork Graph curated query works when my Forge app calls it from a UI Kit resolver. The same query fails when the same app calls it from a Rovo action invoked by the app’s own rovo:agent. Setup Forge app ari:cloud:ecosystem::app/d5a062e1-e206-46e7-af7a-955d63434bc5, development environment, installed in Jira on a Forge demo site (I can share the site in a DM). @forge/api 8.5.0, runtime nodejs22.x, Forge CLI 15.1.0. Scopes: read:jira-work,…

Work Item View 2.0 for Ecosystem Partners

JIRA_ISSUE_CHANGED is not sent to Forge jira:issueContext panels in the new work item view (works in the classic view) Hi team, In the new work item view, a Forge jira:issueContext Custom UI panel no longer gets the JIRA_ISSUE_CHANGED event from @forge/bridge. On the same site, work item, app and user, the classic experience still sends it every time. Switching the view with the work item “…” menu is enough to turn the bug on or off. Reproducer A small app with only a jira:issueContext Custom…

Forge UI Kit app never renders — issuePanel AND globalPage both stuck on skeleton, no iframe in DOM, empty forge logs

Hi all, My Forge UI Kit 2 app never renders anywhere on my Jira Cloud site, and I have run out of local explanations. Hoping someone (ideally Atlassian staff) can point at what would prevent Jira from loading the module at all. Setup - Forge CLI 15.1.0, @forge/react ^11, @forge/bridge ^5, React 18.2, runtime nodejs22.x - Manifest: jira:issuePanel with render: native, function: main (handler: index.run), scopes read:jira-work + write:jira-work - Site: triage-lens.atlassian.net (Jira Free), app…

How are Forge points-quota costs counted for changelog/bulkfetch and search/jql?

Hi @CamdenHuffman, The docs don’t give a cost for search/jql or changelog/bulkfetch. The rate limiting page adds points “for each object involved” on top of a base cost of 1, but it doesn’t define an object, so that worst case is neither confirmed nor refuted. Your resolver calls count. Staff said the same calls made from the gadget’s frontend with requestJira from @forge/bridge are exempt (97828 #133, again in #168). That could change with notice. One partner measured search/jql at 1 + the…