GitKraken vs. Mercurial

The software is easy to use and share within our team. Licensing and setup is straightforward. The product just works and we love it.

Incentivized

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.

Incentivized

• Customizable workflow steps help organize projects
• Time tracking down to seconds helps to estimate sprints
• Burndown charts let you know when to plan your next release

Incentivized

• Branch
• Distributed architecture
• Stable
• Platform independent

Incentivized

• Timing Out - when editing a story or bug, occasionally Axosoft will time out and all changes will be lost
• Viewing past sprints can be hard to locate
• Multiple users within a Story - Axosoft could do a better job managing multiple users on the same story
• User Interface isn't entirely user friendly and looks a bit outdated

Incentivized

• Integration with visual studio
• More integrated tools
• When I install Mercurial I always have to do a hard restart of my computer.

Incentivized

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

Incentivized

I actually like JIRA better, to me the UI is a lot cleaner. Easier to use, and search tickets.

Incentivized

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.

Incentivized

• Productivity bump for developers over previous software
• Code is never gone forever and can be found if needed
• Allows us to collaborate and finish projects faster

Incentivized

• Improve time in merging
• Branching enables us to keep separate version per customer
• Good tool for programmers is sometimes a reason to stay

Incentivized