Depends on the version control and devops process your development teams adopt. Git (via Bitbucket, GitHub, GitLab, etc...) has become the new industry norm, and using pull requests can often provide the same code review features Crucible is used for. However, if you require code review beyond change/diff based (i.e. via pull request), then Crucible allows you to review code with more granular control, such as on per file basis.
It can sometimes be a bit slow to load. A server reboot for us tends to solve that issue. I'm not sure if it is a server issue, or maybe Crucible may have some caching issues.
I wish that you could easily stop the review creation process, rather than abandoning it.
No support issues what-so-ever with Western Digital SSD. This product is so easy to use and configure that there have been no issues that required support other than individual research (online). This product is very stable also, even if dropped, functionality has never been compromised. In 2-3 years of usage, not one major issue at all has been experienced
Gitlab and GitHub are very comparable to Crucible, and would probably be my first choice if those were the tools used for versioning as they are directly linked to git. Crucible was chosen by a current client and I had no choice in its selection. I would probably have chosen GitHub if given a say.
The price is the best option, and a key differentiator, the support and the native application for desktop and for mobile take advantages to others brands or manufactures, this apps are periodically updated this is a plus because others brands only update their apps one per year or more time
I am not involved in the acquisition of Crucible so I cannot comment on the financial investment but I believe it is a necessary tool to have in any software shop, small or big.
As a developer, having Crucible as the code review process is a great asset and will save time and reduce risks which I believe is a positive return of investment.
