Atlassian Marketplace app and version publishing failed for some users over a 7-hour window on September 28, 2026, with affected users receiving a generic "Version publish failed" error across dozens of publish attempts. The root cause was a service account permission issue introduced during weekend maintenance that blocked automated ticket creation required for the approval workflow. Permissions were restored and the publishing and approval workflows are now fully operational; affected users should retry any failed publish attempts.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
The issue impacting Marketplace app and version publishing in the Atlassian Marketplace has been resolved. The publishing and approval workflows are now fully restored, and all services are operating normally.
Root Cause:
During scheduled maintenance over the weekend, the Marketplace app publishing workflow was impacted due to a service account permission issue that prevented automated ticket creation required for approvals. The necessary permissions have since been restored, and the app publishing and submission flows are now operating normally.
Impact Window:
Start: 12:30 AM UTC (28 Sep 2026)
End: 07:30 AM UTC (28 Sep 2026)
Next Steps for Affected Users:
If you previously encountered a Version publish failed error, please retry publishing your app version now. If you continue to experience any issues, please reach out to our team at Developer and marketplace support https://developer.atlassian.com/support .
Thank you for your patience and understanding while we resolved this issue.
Impact
Marketplace app publishing is failing for some users in the Marketplace console. Affected users may see a generic Version publish failed message when trying to make a new app or app version public. Dozens of app publish attempts have been affected.
Current Status
The team is working to restore the approval flow used by the Marketplace console and is validating the service after redeployment. The issue is being investigated alongside recent changes made in internal support services.
Next Steps
Next communication will be sent in 60 minutes, or sooner if there is a significant update.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with