261–270 of 305 posts
RIP defense community using Jira
Classified clouds are a thing. (Also national clouds for unclassified but export-controlled information.) https://azure.microsoft.com/en-us/global-infrastructure/gove...
This sounds like a terrible move and will probably force all medium-size organizations I work with to ditch Atlassian. We have the technical know-how to administer data center versions of their products, but we can’t do shit if they force potential customers to pay for a minimum of 40 000 USD for a license per product. Many of these orgs have multiple Atlassian products so this will probably end up doubling costs on…
We're really larger than "medium-sized", but we're not the kind of company that can or will force everyone to use Jira.
Jira adoption could have happened, but it would only have been possible in a bottom-up, team-by-team basis. And certainly not with a $40000 starting price tag.
As it is, yeah, we're planning on migrating off Jira now.
Earlier quoted context omitted.
Our org uses both Jira Server & Confluence Server - and I’m fairly sure this will make us move away from Atlassian’s products. The split between cloud and server offerings is partly to blame here. My thoughts go out to the businesses that have built plugins for Jira and had to endure the variances between cloud and server, or worse, only catered for the server market. The group at tempo timesheets[1] particularly com…
> I’m hoping that an org like GitLab is able to keep building on and catering for this space. That's not really an option for organizations whose main product isn't code, no?
Earlier quoted context omitted.
I feel like SharePoint and Google Docs are fundamentally different products that Confluence. Looking for a Confluence competitor with permissions, version tracking, templates, and search but don't feel like I have found a good alternative.
I don't think we use version tracking, templates are not really used (but they should be!) and search could be better. We basically use confluence like a wiki, but it's abnormally hard to put info into it.
We're using Jira, Confluence, and BitBucket on-prem at our DC now, on some pretty sizeable VM's with good network connectivity back to head office. Despite that, it feels very slow. Not the occasional 10+ second page load, where you've accidentally clicked something that happens to generate a cascade of cache misses. I can forgive that kind of infrequent performance hiccup. But rather, regular usage, especially of Co…
My experience with Jira makes me think that extensions are a big portion of the problem here. Confluence just sucks though.
We're using Jira, Confluence, and BitBucket on-prem at our DC now, on some pretty sizeable VM's with good network connectivity back to head office. Despite that, it feels very slow. Not the occasional 10+ second page load, where you've accidentally clicked something that happens to generate a cascade of cache misses. I can forgive that kind of infrequent performance hiccup. But rather, regular usage, especially of Co…
I've no recent experience of the on-prem version, but nowadays I have to use the cloud version and it's painfully slow. One common problem I encounter is that after a page loads I might want to search for something in the search box. I'll click it and start typing ... then at some point the rest of the page has loaded including the stupid key bindings which do various random actions on different keystrokes. I don't k…
I use Confluence regularly over a high latency (600ms) link - and this has the surprise / delayed page load you describe, with the newer search features refusing to action your search request until it's loaded & rendered a large overlay on the right-hand side of the screen.
These two attributes make are hugely frustrating, given looking for information is the key function of a wiki.
Earlier quoted context omitted.
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. [1] https://github.com/JetBrains/xodus
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.
Earlier quoted context omitted.
I don't think we use version tracking, templates are not really used (but they should be!) and search could be better. We basically use confluence like a wiki, but it's abnormally hard to put info into it.
Hard in what way?
Earlier quoted context omitted.
They are discontinuing the “Server” product, but continuing “Data Center”… which has more functionality at a higher price, suitable for bigger orgs. You might already be using Data Center, and be unaffected by the new announcement.
It’s surprising to me how many commenters on this post didn’t even read the announcement. When you see that their Data Center offering isn’t going anywhere, it doesn’t seem dire at all.
Earlier quoted context omitted.
My experience with Jira makes me think that extensions are a big portion of the problem here. Confluence just sucks though.
What about Confluence sucks specifically? I share your view but how could it be better?
2. Editing is a clunky process. Not only is the UX subpar, it never loads all the possible widgets you can insert, making dynamic content a pain.
3. Awful search. It always manages to find internal process documents from 2014 and not the service pages I actually want.
4. Tough to reorganize content. Moving a page around is just hard enough that people tend not to do it, resulting in really poorly organized content.
Honestly, I’d be happier using notion or just GitHub wikis. But the main benefit of putting our docs at wiki.$COMPANY.com is that I can guarantee discoverability for other teams, so we’re kinda stuck with it.