Jira Mobile Forge Transition + Marketplace Apps Gap Blocking Field Work - Are You Affected?

Question

Hi everyone,

I wanted to raise awareness of an issue that’s having a significant and growing impact on our operations, especially as Atlassian continues the transition to the Forge platform.

Like many organizations, we rely on Marketplace apps to extend Jira beyond its native capabilities. These extensions are essential to how our workflows function, not optional add-ons.

✅ Historically:
Third-party app functionality was available to users, including in many cases within the mobile experience, enabling teams to complete end-to-end workflows regardless of location.

⚠️ Current state (after the Forge transition):
As apps are being migrated or rebuilt on Forge, support for this functionality in the Jira mobile app is being lost or is no longer available.

🚫 The problem

Our field teams depend heavily on the Jira mobile app to perform their work on-site. Key parts of their process, such as completing required workflow steps tied to app-driven functionality, are no longer accessible.

👉 The impact

This creates a critical operational gap:

* Field workers are unable to complete required actions
* Work cannot be properly logged in real time
* Processes that previously worked are now effectively blocked on mobile
* This represents a regression in capability, not just a missing feature

For teams operating in the field, this significantly disrupts productivity and undermines confidence in the platform. And with the rapid migration to Forge we have little time to figure out work-arounds.

📣 If you’re impacted, please help amplify this

Atlassian is tracking this here:
🔗 https://ecosystem.atlassian.net/browse/FRGE-1492

Public ticket is also open here:
🔗 https://jira.atlassian.com/browse/JRACLOUD-95236

If this affects your team, please:

* Vote and watch the ticket
* Share your specific use case and business impact

The more visibility this has, the more likely it is to be prioritized.

✅ Why this matters

Jira’s strength lies in its ecosystem. If Marketplace apps lose meaningful support in mobile as part of the Forge transition, it creates a serious gap, especially for organizations with teams in the field.

Restoring and supporting this functionality in the mobile experience is essential for maintaining Jira as a viable, end-to-end solution.

Thanks, and I’d be very interested to hear how others are navigating this transition.

Robert Eiser · Answer

Thanks @Martin Luethi _Mobility Stream_ I appreciate learning about your mobile app alternative. This will be helpful as I investigate alternatives and work arounds.

It is ironic and highly frustrating that a solution to the issue Atlassian has created by not supporting 3rd party Forge apps in its own mobile app, is to have companys move toward even more 3rd party apps.

Martin Luethi _Mobility Stream_ · Answer

Hi @Robert Eiser ,

I completely understand the concern. For organizations with field-based teams, losing access to critical app functionality on mobile can break established workflows and create real operational challenges.

We've worked with many customers who rely on Marketplace apps such as Elements Connect, Tempo, Dynamic Forms, and many others that are key to their workflows. Access to these capabilities from a mobile device is often essential for completing work in real time and may block issue creation, status transition, and so on.

If you're willing to share which Marketplace apps and use cases are most critical to your team, we’d be interested to learn more. At Mobility Stream, we’ve taken a native API-based approach rather than relying on web rendering, which has allowed our mobile app to continue supporting many Marketplace app integrations without being impacted by the Forge mobile limitations.

Also happy to help pushing this functionality with Atlassian! If you want to get in touch, you can use this email address.

Best regards,

Martin