moving from JSM Server to JSM Cloud: Cloud is just a piece of crap

[Chris Schneider]

Dear Atlassian,

we are on our way to migrate from our Jira Server infrastructure (Jira, Assets (Insight), Confluence) into the Cloud. You basically force your clients to do so. (BTW: cloud licenses are 30% (!) higher, than our Server licenses.)

In our JSM, we heavily rely on Assets. We do have 4 source systems providing 30+ objecttypes into Assets. In our Jira Server version, this works perfectly fine, in cloud, this is just a piece of crap. I have invested 60+ hours to figure out, to find the best way to get data into the cloud and I have paid ~10'000 USD to our Enterprise Service Bus Integration Partner to program the interfaces between our source systems and the Assets Rest API. We are not yet finished and not yet up and running.

The documentation of the Rest API is a good start, but there are a lot of very basic information missing. (Assets external imports workflow (atlassian.com))

We stumble accross one bug after another. This is very, very annoying. Our cloud move project is just a big waste of time.

List of bugs affecting us:

• [JSDCLOUD-11727] Partial data imported as part of Discovery imports - Create and track feature requests for Atlassian products.
• [JSDSERVER-11099] Insight Discovery export to Cloud, when having a Discovery Agent Result - Create and track feature requests for Atlassian products.
• [JSDCLOUD-11162] Insight Discovery import of a large Scan Results zip does not work - Create and track feature requests for Atlassian products.
• [JSDCLOUD-11178] Insight external import to run as the generator of the OAuth token - Create and track feature requests for Atlassian products.
• [JSDCLOUD-11890] Sending a PATCH request to Insight's External Imports will clear the “Filter data source by IQL“ setup on Object Type mappings - Create and track feature requests for Atlassian products.
• [JSDCLOUD-11891] Add ability to set "Filter data source by IQL" via REST on External Imports - Create and track feature requests for Atlassian products.

I fully understand that Atlassian has a very glossy marketing and that you would like to have customers, who live for your products. I was one of those - not anymore.

I don't want an appology, just stop your glossy marketing, get your ressources together and fix those bugs.

Chris, a very unhappy customer

[Alex Koxaras _Relational_]

Duplicate https://community.atlassian.com/t5/Jira-Service-Management/moving-from-JSM-Server-to-JSM-Cloud-Cloud-is-just-a-piece-of/td-p/2179776