81–90 of 127 posts
Earlier quoted context omitted.
IMO bitbucket is okay. Its UX for PRs is amazing, 1000x better than Githubs. Especially its side by side diff. This concludes, and fully encompasses, everything good that I have to say about Atlassian products.
Atlassian bought Bitbucket after it was already mature. That's why!
I'm my experience almost everything that Atlassian makes is total garbage. Bitbucket, Jira, Confluence, etc. are all horribly slow to the point of being unusable and most of it has very poor UI/UX. I pretty much don't recommend anything they make. It's not surprising at all that a fundamental feature of a wiki, search , doesn't work very well.
Atlassian products feel like raw database frontends. I feel like each screen in each Atlassian product is always exactly a database table, being presented to me as an auto-generated form. Might as well use SQL directly.
Searching corporate wiki is pretty difficult, because contrary to something like Google, you can't use context of a search query to recommend content. * First you have a few occurrence of the same search query in your search history (because only a few people searched similar words in the past) * You can't either use synonyms of remove stop words to recommend better content (IT, can means "information technology, or…
It does partial matches anywhere in a word, supports every language even in the same document, and even has regex support for those who need it. Update instantly with instant filters.
It can find things like 168.0 in 192.168.0.1 which the existing confluence search cannot for example. Or search for AKIA credentials /AKIA[A-Z0-9]{16}/ I have heard people describe it as Agolia for confluence which makes me happy.
https://marketplace.atlassian.com/apps/1225034/better-instan...
As for why their search is so bad? It's probably due to how they apply permissions. Every permission for their search needs to apply per search per user. It makes it complex and hard to apply changes, making it hard to improve things. I imagine it's one of those parts of confluence that is a major pain to work with.
I think a lot of this is also due to their cloud migration. When using the server version they were allowing you to host yourself you could store the index on disk. With cloud they suddenly need to keep the index state somewhere persistent, but they also want to dynamically scale up and down.
Lastly, they also apply stop words, stemming and such, using out of the box lucene. Lucene is a great tool, but it can also be a pain to work with. You can see problems when you mix languages on the page too, such as having Thai, Chinese and English on a single page which confuses the Lucene tokeniser.
Earlier quoted context omitted.
IMO bitbucket is okay. Its UX for PRs is amazing, 1000x better than Githubs. Especially its side by side diff. This concludes, and fully encompasses, everything good that I have to say about Atlassian products.
Atlassian bought Bitbucket after it was already mature. That's why!
If you want best of both words, you can use the "Favorite Pages Macro" on any page to reference all of the pages that you have saved for later, which makes keeping that page up to date with your latest changes to saved pages trivial.
I'm my experience almost everything that Atlassian makes is total garbage. Bitbucket, Jira, Confluence, etc. are all horribly slow to the point of being unusable and most of it has very poor UI/UX. I pretty much don't recommend anything they make. It's not surprising at all that a fundamental feature of a wiki, search , doesn't work very well.
Atlassian products feel like raw database frontends. I feel like each screen in each Atlassian product is always exactly a database table, being presented to me as an auto-generated form. Might as well use SQL directly.
- Atlassian probably
My colleagues and I have been grumbling for ages that our instance of Confluence must be really badly configured. If you put in a single word search term, there will be lots of results, but no guarantee that any pages containing that word in the title (or body), will appear above ones where it doesn't.
The search problem was solved long ago by Apache Solr/Lucene. Although this may not be true for multiple languages.
Earlier quoted context omitted.
We use bitbucket cloud, and the PR UX is awful. Which version are you using? Are you using a browser extension or something? Compared to UpSource or GitHub, Bitbucket PRs are very rough.
Bitbucket Cloud and Bitbucket On-prem are two entirely separate products. It makes about as much sense as you can expect from Atlassian. The former was a Mercurial thing that they purchased then later removed Mercurial support. The latter used to be called Stash. We moved from Bitbucket On-prem to Gitlab and I must admit I do miss parts of Bitbucket's UI. It was much easier to find reviews you needed to do and it was…
Ultimately we’ve decided to build on top of our server platforms and target companies with 1000+ employees from day one. That decision had a huge impact on how we approached performance and what features we prioritised. The hierarchy of projects and permissions associated with them as well as the way we designed Pull Requests are good examples of that.
It was the right decision at the time, even if the product happened to be different in cloud and server, which did lead to some confusion. But Stash customers were really happy with the product.
I'm my experience almost everything that Atlassian makes is total garbage. Bitbucket, Jira, Confluence, etc. are all horribly slow to the point of being unusable and most of it has very poor UI/UX. I pretty much don't recommend anything they make. It's not surprising at all that a fundamental feature of a wiki, search , doesn't work very well.
Atlassian products feel like raw database frontends. I feel like each screen in each Atlassian product is always exactly a database table, being presented to me as an auto-generated form. Might as well use SQL directly.