Changes to Developer and Marketplace Support: New Platform Experience UPDATE: Migration Postponed

:warning: Update (September 27, 2026): Migration Postponed :warning:
During our scheduled migration over the weekend, we encountered an unexpected issue and made the decision to roll back and postpone the transition at this time.

What you need to know

  • Continue using the current portal: Please continue submitting tickets via https://developer.atlassian.com/support and managing existing ECOHELP tickets.
  • No impact to active tickets or SLAs: All existing tickets remain active and uninterrupted in the current portal, and our support team is operating as usual.
  • Rescheduled date: We are working through the root cause and will provide an updated migration timeline well in advance of our next attempt.
    Thank you for your patience and understanding.

As part of our ongoing commitment to the Marketplace partner and developer experience, we’re migrating our support ticketing system to Atlassian’s standard support platform — bringing you a more unified, streamlined experience built on the same infrastructure that serves all Atlassian customers.

What does this mean for you? Starting Sep 28, 2026, you’ll notice a new support portal URL and a refreshed experience with faster, more integrated workflows. All tickets will automatically carry over, so there’s nothing you need to do.

What’s changing

  • New support URL: You’ll access support through support.atlassian.com/contact instead of the current Developer and marketplace support portal

  • Existing tickets are migrated: Any open tickets will be available under the new system. You do not need to re-submit anything.

  • Improved portal experience: View all your tickets in a single location.

  • Smarter identity recognition: We’ll know who you are automatically based on your Atlassian account.

Submitting a support request

Before After 2026-9-28
Support URL ecosystem.atlassian.net/servicedesk/customer/portals support.atlassian.com/contact
Portal view Simple JSM ticket creation portal Intelligent Contact Form
Identity recognition You must provide your Partner ID and App ID manually We recognize you automatically based on your Atlassian account
Request types shown All request types shown to everyone Tailored to your role. You’ll only see options relevant to your Marketplace or developer activity

What’s NOT changing

  • Same team, same expertise: The same support engineers you work with today are the same people supporting you after the move.

  • Same SLAs: Your response time and resolution commitments remain identical. No change to your entitlement.

  • Same internal escalation paths: Escalations and priority handling all work the same way.

  • Same Partner Tier recognition: Top Marketplace partners continue to receive prioritized support.

  • Same scope of support: We still cover the same request types: development blockers, app review issues, Marketplace listing questions, Forge platform support, and more.

  • App reviews and security programs stay on EAN: Marketplace app review tickets and security program tickets (in the ECOHELP/AMS projects on ecosystem.atlassian.net) will continue to be managed there. However, you can view and access these tickets directly from support.atlassian.com/requests — no need to switch portals to track them.

Your Customer Support Portal (where you track your tickets)

Additionally, the portal where you view and manage your open cases is also getting an upgrade. The URL is changing to support.atlassian.com/requests, and the experience is now unified with the rest of Atlassian support.

Before After 2026-9-28
Portal URL ecosystem.atlassian.net/servicedesk/customer/portals support.atlassian.com/requests
Ticket visibility Visible only in the Developer & Marketplace portal All your tickets (product support and developer support) will be visible in one place
Escalating a case “Escalate” option available from the ticket “Escalate issue” button available in the portal when your case is active
Resolving a case “Resolve” option in the portal “Resolve issue” button available. You can also accept or reject a suggested resolution from our team
Reopening a closed case Comment on the ticket to reopen Use the “Reopen” link in the portal, or comment and our team will follow up

A note on Marketplace app reviews and security programs

Marketplace App reviews and security program tickets are managed in the ECOHELP and AMS projects on ecosystem.atlassian.net (EAN), and this will not change.

  • Viewing your tickets: Even though these tickets live on EAN, you can access and track them directly from support.atlassian.com/requests once you’re logged in. You don’t need to visit EAN separately.

  • Applying for a security program: If you navigate to support.atlassian.com/contact to apply for a security program, you will be redirected to create your ticket on EAN (ECOHELP project) as usual. This is expected behavior and the redirect is intentional. Your application will be handled by the same team through the same process.

What you need to do

  1. Update your bookmarks — After 2026-9-28, use support.atlassian.com/contact to raise new support requests and support.atlassian.com/requests to track your cases.

  2. No action needed for open tickets — We’ll migrate them for you. You’ll receive a comment on any active ticket with the new URL.

  3. Check your Atlassian account — Make sure your developer/partner email is associated with your Atlassian account so we can recognize you automatically.

Timeline

  • Friday, Sep 25, 2026 (5 PM PST) through Monday, Sep 28, 2026 (10 AM AEST) Migration weekend. Important note: new tickets cannot be submitted during this window. A banner will be displayed on the contact form.
  • Monday, Sep 28, 2026 (10 AM AEST) New platform live. Submit new tickets via support.atlassian.com/contact

Can you also work on reducing the bureaucratic burden placed on partners?

It seems to be ever-ratcheting despite advances in AI that should result in the opposite.

Thanks @DanielR, that’s a welcome change!

Thanks @DanielR

Any change there is an API we can use like ecosystem has?

Commenting appears to have also been turned off during the migration.

Entire developer ecosystem ticket system down for three days.

One day notice via CDAC and negative one day notice via changelog.

I guess submitting new plugins or updates also don’t work, I keep getting errors when submitting so it should be the ticket system is down.

Hi Nathan,

Fair callout on the changelog - we should have posted this there as well, in addition to the Partner Portal announcement.

As part of our platform migration that started Friday, September 25 at 5:00 pm PST, commenting, changes and new ticket submissions are temporarily locked to prevent data loss while tickets are transferred.

Everything is tracking on schedule to be fully back up by Monday, September 28. Thanks for your patience while we complete this project.

Would this be impacting publishing new app versions?

We’re currently unable to make new Data Center versions public in the Marketplace vendor portal.

Interestingly, we have historically published both DC and Server versions (even though Server is a distant memory at this point - don’t ask me why, we just figured that since our DC and Server versions are equivalent we would publish both). That now seems to have ended and we get an error saying that server publishing is disabled for our app key.

So there’s definitely changes around version publishing happening, and it seems like something is currently broken.

Hi Scott,

This migration only impacts our support ticketing system and is separate from the Marketplace Vendor Portal and app version publishing infrastructure.

The error you are encountering is likely related to Server publishing restrictions rather than the support platform migration. Please give us a day to complete the service desk migration, and then reach out to us by opening a ticket at Atlassian Support (under Developer & Marketplace Support) so we can take a closer look and help you get the new version published.

Ok. I’m less concerned about the Server issue and more concerned that we can’t push out a DC update at the moment.

Also, even though this is a planned outage, should the status page show that Marketplace support is current unavailable?

Otherwise why do we even have these status pages?

Appreciate the nudge on this. The Statuspage is now updated to reflect the planned maintenance.

Did you see my battle earlier this month? A team initiated 12-hour API outage and then refused to report it before, during or after. I exhausted all the channels publicly and privately, at the most senior of levels. Nothing changed.

During our scheduled migration over the weekend, we encountered an unexpected issue and made the decision to roll back and postpone the transition at this time. I’ve updated the top of the post with the info you need to know. Thanks!

Still unable to make new DC app versions public as of this morning (after the status page confirmed that everything should now be operational).

I guess that means a support ticket is incoming…

Hello @scottohara ,

Apologies for the trouble.

The publishing failures were an unexpected side effect of the support platform migration attempt, and our engineering team is actively working on the fix.

You can follow the incident status here:
:link: Service Disruption: Marketplace App Version Publishing

Thank you for your patience and understanding while we work to resolve this.

Best regards,
Nicolas Grunberg
Ecosystem Support Manager