GitKraken's commit graph helps visualize branch structure and commit history. It helps verify recent Git actions on the repo, and also shows who made what code changes and when, so it’s easier to track down when a bug was introduced and revert back to a previous version. GitKraken Client is a Git GUI that detects and alerts users of potential conflicts so as to prevent them from happening. With itsuser Activity Status, the user can know who is online in the GitKraken Client.
$1,250
per installed license
Mercurial
Score 9.1 out of 10
N/A
Mercurial is a free, distributed source control management tool. It handles projects of any size and boasts an easy and intuitive interface. Mercurial handles projects of any size and kind. Every clone contains the whole project history, so most actions are local, fast and convenient. Mercurial supports a multitude of workflows and can enhance its functionality with extensions.
N/A
Pricing
GitKraken
Mercurial
Editions & Modules
Installed by You
$1250
per installed license
Hosted by GitKraken
Customized according to the amount of team members.
No answers on this topic
Offerings
Pricing Offerings
GitKraken
Mercurial
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
GitKraken
Mercurial
Features
GitKraken
Mercurial
Version Control Software Features
Comparison of Version Control Software Features features of Product A and Product B
Axosoft is well suited as a project management tool for software teams looking to track workloads. Great tool for categorizing features, tasks, bugs, or a customized category into sprints. Companies can take advantage of the tracking aspects to create burndown charts or just to track employee time. I would say it is less appropriate for small task management like a to-do list type application because it has so many features that would go to waste. Furthermore, Axosoft is more geared towards development teams, but you could use it across departments if needed.
If you generally think that to develop software you have to choose one repository, then in my opinion you have to choose between Mercurial and Git, there is not other solution. Mercurial also has a good merge tool which i can recommend. This gives you the flexibility to push just the "part of the feature", and is much better suited in the case where the "part of feature" and some other "part of the feature" both contain changes to the same file.
A bit hard to use, or a steep learning curve. The UI isn't super intuitive at first, it took me awhile to pick it up and I had to get someone to basically show me what they recommend I set my filters and UI to.
This might be a case of improper setup but when making tickets, there isn't an auto response, so we get a lot of duplicate tickets if a conversation happens on the emails before someone takes the case and replies through OnTime.
Once you get the hang of Axosoft, I think it's easy to use however... getting the hang of it takes quite a bit of time. Additionally, once Axosoft makes an update, it can be difficult to find your bearings again. Like I said, once you know how to use the product, I think it's easy but it takes a bit to become comfortable and confident with Axosoft
When we chose Mercurial it was more popular from perspectives than Git and we have too many problems with the Microsoft team foundation solution. We also want to move from a centralized version of source control to a distributed one. We also were working more and more via the Internet with our source control so distributed version was only solution.
Axosoft has positively affected the time management of our employee resources
Axosoft has shown us where we have inefficiencies in the organization
Axosoft has allowed us to track projects better, get them out on time allowing for more projects to be scheduled and, in turn, increased our subscriber count.