BugHerd vs GitLab

BugHerd is excellent for tracking feedback on websites or other web-based material (such as our online courses, delivered via LMS): the ability to easily and quickly move from the kanban board to the site of the issue, the rich features (auto-screenshots with mark-up; comment threads; assignments and @-mentions; status tracking); and the company's responsiveness to requests makes them great to work with.

Gitlab is a good platform for collaboration with the team, version control, and optimized way to handle the modifications in the project. GitLab is less appropriate in some cases, though it has a lot of options for integration, new users find it difficult to integrate; there is also room for improvement.

• The screen capture tool is terrific and allows web-based issues to get added and uploaded without any saving, copying, or resizing.
• The widget that opens via a Chrome extension is intuitive and it's easy to toggle the feature on and off. If it's on, you can see all the other reported bugs on that page to help your team avoid multiple reports of the same issue.
• The way the tool creates a new ticket for each bug and then allows you to adjust the status on it is helpful.
• I enjoy the conversations and tagging features within each bug ticket.

• The way they have managed to provide the version management aspect using git with project setup and users is mesmerising cause there's no product out there that gives this freely.
• Continuous updates and hearing what users need is what the product engineers at GitLab are doing best. They come back to you with exactly what you need every while.
• Quality features, Latest tech integrations have made the end-to-end solution very flexible and agile.
• CI/CD tools implementation with pipelines and deployment strategies is just making the job for Infra teams smoother.

• It would be nice if it offered more integrations.
• Workflow could be a little more sophisticated.

• Sometimes, it is really challenging to manage conflicts when a lot of merge requests are coming for multiple separate branches to the main branch.
• One area of improvement for the software, is sometimes, the interface can work slower
• A few times, we have faced difficulties testing CI builds locally.

Gitlab is the best in its segment. They have a free version, they have open-source software, they provide a good service with their SaaS product, they are a fully-remote company since the beginning (which means they are fully distributed and have forward-thinking IMO). I would certainly recommend them to everyone.

BugHerd is an easy-to-use, highly intuitive tool that fits seamlessly into our web development process. It is easy for all users to use, web developers, project managers, testers and clients. Clients are able to easily pin bugs and provide explanatory feedback that allows our team to fix what is broken and incorporate client feedback.

The web console management is superior and I would have given Gitlab a 10, but sometimes it is hard to find documentation about a configuration setting in the gitlab.rb configuration file. As we move everything to code that means moving our CVS tools to code as well - and Gitlab to code. The usability of Gitlab from the end user's perspective is superior and the usability from the operations team is very good and getting better but there could be a little improvement in the gitlab.rb config file layout and documentation.

Truthfully, we have had very little need for BugHerd support, as the tool is intuitive and does not have many bugs of its own. They have a pretty solid help/FAQ section and their support people have been reasonably responsive the few times we have needed to contact customer support. We have had our issues resolved and questions answered.

At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft

It's better than everything else we've found. So far if we were going to find something better for us -- we'd probably need to make it ourselves.

We have a small custom code development group. We only needed a basic entry-level code management repository. Gitlab meets our needs and is very price advantageous compared to others on the market. We also needed a system that is easy to administer and easy to grant access to our limited-size user base. Gitlab does what we need and gives the necessary flexibility for application support, user administration, and code/version control needs to be required.

• Simple, easy bug and task tracking is the name of the game. At a glance you can see when in the queue a specific bug is and who is working on it.

• We are moving towards Gitlab only as our SCM & CI tool. So it would be an alternative to Jenkins. Saving our licensing cost there.
• We have also stopped using Confluence & using Gitlab for our documentation purposes. Reducing cost there as well.