Not a good week to be an Altassian Marketplace developer

Marketplace General Discussion
1

First, there was an unannounced CSP breakage (which incidentally, there was promised to be a followup changelog entry on 23 May, which is yet to appear).

Next, there was a breakage to the Marketplace REST APIs, with no Statuspage entry until 11 hours after the incident began (posted at the time the incident was resolved).

Now today I just received this email:

[REDACTED]-staging has been deleted due to inactivity

[REDACTED]-staging has been deemed inactive after having no apps or managed accounts in the last 180 days.

In an effort to clean up inactive organisations and increase productivity, [REDACTED]-staging has been deleted.

If you want to see your remaining organisations, you can do so by going to admin.atlassian.com. The deleted organisation ([REDACTED]-staging) will no longer be visible in Atlassian Administration.

If you want to keep your organisation, we suggest you contact support within 15 days from receiving this email.

When you contact support, include your organisation ID: [REDACTED].

The organisation mentioned here (“[REDACTED]-staging”) is our sole pre-release testing environment for all of our cloud apps. This is a free developer instance that we have had for approximately 10 years at this point, and is regularly in use by our team (as recently as yesterday).

Needless to say we have contacted support to request that the organisation NOT be deleted.

What is going over there at Atlassian? It is becoming harder and harder to maintain confidence in this ecosystem, yet Atlassian are demanding an extra 5% revenue share from our Connect apps next year.

It is hard to see how they have earned this increase at this point.

5 Likes
2

worst_week_so_far_simpsons_meme.jpg

I had a potential customer reachout to say they’ve been unable to install an app trial, and that they’ve been in a 3 month-long ticket with Atlassian support.

Like opening a new storefront and hearing customers outside complaining that the door won’t open while the landlord shrugs: Can we finally get useful info in app install error messages?

I think/hope I’m now in contact with the right internal decision makers after 4+ years of reporting the issue. TBD.

3

Also one thing that has changed without further notice this night because my pipelines are failing… The Atlassian JSON format with all the Server / Data Center releases have changed… (e.g. https://my.atlassian.com/download/feeds/current/jira-core.json)

It previously was JSONP (JSON with Padding) and the version objects itself are also different.

Old object:

{
    "description": "8.21.1 (Windows 64 Bit Installer)",
    "edition": "Standard",
    "zipUrl": "https://www.atlassian.com/software/jira/downloads/binary/atlassian-jira-core-8.21.1-x64.exe",
    "tarUrl": null,
    "md5": "ce4027c78472f54fe05bdea44b3e71e6",
    "size": "390.4 MB",
    "released": "26-Jan-2022",
    "type": "Binary",
    "platform": "Windows",
    "version": "8.21.1",
    "releaseNotes": "https://confluence.atlassian.com/display/JIRACORE/JIRA+Core+8.21.x+release+notes",
    "upgradeNotes": "https://confluence.atlassian.com/display/JIRACORE/JIRA+Core+8.21.x+upgrade+notes"
  }

New object

{
    "id": 60363,
    "name": "10.6.1 (ZIP Archive)",
    "edition": "Standard",
    "status": "Current",
    "type": "Binary",
    "size": "560.5 MB",
    "dateAdded": "2025-05-20T05:06:14.892-0500",
    "zipURL": "https://www.atlassian.com/software/jira/downloads/binary/atlassian-jira-core-10.6.1.zip",
    "tarURL": null,
    "priority": 6,
    "version": {
      "id": 32326,
      "name": "10.6.1",
      "releaseNotesURL": "https://confluence.atlassian.com/display/JIRACORE/JIRA+Core+10.6.x+release+notes",
      "upgradeNotesURL": "https://confluence.atlassian.com/display/JIRACORE/JIRA+Core+10.6.x+upgrade+notes",
      "date": "2025-05-20T05:06:14.892-0500",
      "buildNumber": 1006001,
      "cvsTag": "https://svn.atlassian.com/svn/private/atlassian/jira/release/10.6.x",
      "product": {
        "id": 10270,
        "name": "JIRA Core",
        "key": "jira-core",
        "downloadUrl": "https://www.atlassian.com/software/jira/core/download"
      },
      "uuid": "5a0e367f-3f37-417e-b3bb-775e925a2b7a"
    },
    "productId": 10270,
    "md5": "f54c1154891efd88a34ce594f4a6cbb9",
    "sourceURL": null,
    "downloadLabels": [
      {
        "downloadId": 60363,
        "labelName": "Windows"
      }
    ],
    "uuid": "fd6e51f3-cdb4-4a2f-b068-91cefc663c56"
  }

The only good thing is, that also the archived feed has the “new” format. Just an observation, for some older releases the zipURL has changed from https to http.

//EDIT: Back to old format since 29.05.

4

I am not a partner or a developer - but a customer, and Atlassian Billing and such has gone insane, I have a hard time figuring it out. We needed to reset a site, but was on “New Billing experience”, so Atlassian needed us to move to “Old expericence”… Took +2 weeks for some extreme slow “Customer Advocate” with several escalations and I am never sure it was done correctly as an important statuspage ended up under the test site…

We ended up creating yeat another site for the tests…

And we suddenly got a lot of apps cancelled on a site - an investigation showed they had been in “grace” mode for 90 days, but a customer cant see that the Apps are in grace mode and then self-ensure payment/subscription - that is only the billing partner. Ive come to the conclusin that nomatter what the type of billing expenricene it is (new/old) - its mainly a bad expenrience…

3 Likes