You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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:
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
Community moderators have prevented the ability to post new comments.