Yes, there still is no easy way to migrate Tempo data from Server to Cloud. Their advice is "there's an API - good luck" [1].
Gitlab is great for their developer niche, but the relatively weak issue tracker and wiki lets them down for more general use. Still, Gitlab is a great company with momentum and a roadmap. Feel free to join us [2] in looking at such alternatives.
Please stop doing this. Fishing for product insight on such broad opinions in an open forum does a disservice for Gitlab the product and the team. If it was a natural question... But this is so canned, every gitlab employee here does it, sounds flaky and impersonal. Almost troll-like, maybe even arrogant tbh.
You really don't know why Gitlab is not an issue tracker like Jira is? I'm sure you do, or at least you should know. Being an issue tracker like Jira is not even a bad thing! So why try to look like you think you can be as bad as Jira?
sorry that it came around this way. I was really interested in your honest opinion, as my personal experience with Jira is limited at this point with 7 months into my new role. I have been asked about it during past GitLab trainings in my old job, but never used it in production myself. May sound weird, but I learn the most from users sharing their experiences :) Hence my question, it would help my research.
Atlassian's Cloud products were initially (~2009) just the Server products with a few plugins bolted on to unify the UI, deployed in bulk. Over time the backends diverged, and here we are.
It's an difficult position Atlassian are inflicting on tens of thousands of customers. Atlassian's self-hosted products are uniquely flexible, being built on a plugin architecture, and many orgs have indeed customized Jira extensively with plugins, notably ScriptRunner [1]. Atlassian's Cloud plugins have their APIs, but have nothing like the same flexibility. A lot of functionality just isn't possible in the Cloud architecture. It's a bit like Firefox moving from XUL to an extension API.
In my opinion, the most customer-respecting way forward would be for Atlassian to open-source their discontinued Server product line. Go to the "open core" model with the clustered Data Center product as the upsell. This avoids screwing over their customers, and if their Cloud product really is as good as they say, customers will migrate to it naturally over time. It's the kind of damn-the-torpedoes move I think Mike CB would like.
But over the next 3 years, lots of painful migrating or evaluating-of-alternatives will need to happen, and perhaps a non-Atlassian forum for sharing experiences will help.
I promoted it upthread (though I have no connection to JetBrains), but I'd note that YouTrack and their other team products have extensive Java and REST plugin APIs so they're also very customisable. Actually YouTrack lets you write workflow logic in JavaScript too.
I would like to like YouTrack, but I've always been put off by own custom database [1]. I like my data in relational databases. SQL is the ultimate read-write API. Jira (unintentionally) stands on the shoulders of giants in this regard.
Problem is that DB schemas are unlikely to be exposed as a real API by any app. It may feel like an API but actually writing software that pokes DB tables directly would just create the kind of support and upgrade headaches that presumably are driving Atlassian to this decision.
The other advantage of the JB approach is it's one click install and upgrade. No schema migrations, complicated issues with DBA hoarding permissions etc.
> open-source their discontinued Server product line
little did you know, the source code for atlassian server products is already available for any paying customers. It's not FOSS, but if you need to run this yourself, and customize it, it's already possible. But of course, you will be responsible for keeping it updated (patching vulnerabilities from libraries etc).
I mean under an Open Source license, which the Atlassian Software License Agreement [1] is very far from being. It forbids you to even redistribute patches between licensees.
I’ve never succeeded to compile it, and like Android, most of the code is in non-public plugins. I’ve been a developer for long and we can only use it to look at algos of the core product, but not execute them.
Plugins are great until you crash your standup board because the “Recycle” plugin put stories somewhere you can’t see but also didn’t remove the story from the sprint, causing permission issues.
A lot of what makes Jira so broken is that it is way too flexible, and this flexibility has costs in terms of performance and stability. There’s a damn good reason why I used Chrome back in the XUL days for FF; because XUL FF was not performant or stable for me back then.
Ha! From the get go I remembered I heard this song in a Studio Ghibli movie, then a google search quickly told that it was on From Up On Puppy Hill :-p. I love the Internet.
Just once, humming (not particularly well), not singing.
The song in question is sung with a very clear voice, with minimal instrumental backing. That may suggest the limiting factor is Google's ability to parse songs, rather than users' ability to hum them.
That wouldn't answer the question. Searching a song that you remember from the past is nothing like listening to a song on YouTube and then immediately trying to sing it back to Google.
Tried it with soundhound [0] (was called midomi when I used it as a flash app many years ago) just for giggles and it found a different version of the same song first try as well.
'The song is best known under the alternative title "Sukiyaki". In Japan it refers to a Japanese hot-pot dish with cooked beef, the word sukiyaki does not appear in the song's lyrics, nor does it have any connection to them'
"Ei wrote the lyrics while walking home from a Japanese student demonstration protesting against a continued US military presence in the country, expressing his frustration at the failed efforts."
"An instrumental version of the song was played by NASA over the radio for the Gemini VII astronauts as mood music, thereby becoming one of the first pieces of music sent to humans in space."
Gitlab is great for their developer niche, but the relatively weak issue tracker and wiki lets them down for more general use. Still, Gitlab is a great company with momentum and a roadmap. Feel free to join us [2] in looking at such alternatives.
[1] https://tempo-io.atlassian.net/wiki/spaces/THC/pages/8969584...
[2] https://www.goodbyeserver.org