Keeping our developer community open and respectful

Announcements
12

Hi @ChrisHemphill1 ,
Just to give you an impression of what we have to handle as a developer, here the things I had to “experience” in the last couple of weeks:

  1. Error in the newly released API for Live Docs, needing triage on my side and programming a workaround Please test & update your Confluence Cloud apps to function in Live docs by May 30, 2025 - #16 by marc
  2. Atlassian unannounced uses a new origin, leading to CSP errors in apps, requiring an emergency release to fix it from our side, New CSP warnings from *.atl-paas.net. Weeks later a “retroactive” changelog is posted with no acknowledgement of the problems, https://developer.atlassian.com/cloud/confluence/changelog/#CHANGE-2554. No report on the statuspage.
  3. Macro PDF export stops working, Exporting macro to pdf not working - #15 by marc , no report on the statuspage.
  4. Confluence starts copying page properties, Confluence Page Copy is now copying entity properties? . This lead to multiple tickets, confused customers which also opened tickets, there was no changelog entry and no report on the status page.
  5. Atlassian requires us to use new packages for development, yet does not use the packages themselves. Also releases a package with no code on npm, New @atlassian packages on NPM .
  6. We have a new paid license without payment. First line marketplace support thinks we are a solution partner and advises us to do something with billing, then nixes the license, then starts a new trial. Second line marketplace support is more helpful, however now we wait until the new trial is expired.
  7. Announcement of a new Forge cli version, Changes in the next major release of Forge CLI - #2 by marc . It seems Atlassian is not aware of the security vulnerabilities. This is also visible in https://jira.atlassian.com/browse/ECO-712 with low priority. I had opened an ECOHELP ticket earlier about the security vulnerabilities and was relegated to this ticket.
  8. Trying to add a resolver to a Forge app. Getting weird errors. Need to search through CDAC to find the issue: Taking the Ecosystem Forward: An Update on the Future of Connect - #16 by scottohara , which is a new low for me for Forge.

Given such an abundance of difficulties for marketplace vendors, it’s hard to keep believing that Atlassian does enough. These where all errors/difficulties. On top of that we need to move to Forge and (lastly) serve our customers?

3 Likes