BugHerd works for us!
Use Cases and Deployment Scope
We use BugHerd for tracking feedback, changes, and fixes during the development and testing of our STEM/Tech-focused courseware products. Our product development, maintenance, SMEs/faculty experts, and Alpha Testers teams use BugHerd for logging and tracking issues and their resolutions throughout the development process.
Pros
- Link feedback directly to the location in our courses.
- Provide flexible updates for our enhancement requests.
- Provide an intuitive, easy-to-use, and feature-rich interface.
Cons
- The Dashboard feature has been in Beta for some time; could use an update there.
- The addition of the ability to associate multiple URLs with a single Project was welcome, but better handling of that feature in coordination with the Open Website button would be nice.
- Being able to set up templates for quickly creating Projects with similar layouts (columns with custom names; default Members) would be very welcome.
- The ability to customize the Priority status codes, in number, name, and color would also be nice.
Most Important Features
- Ease of use and integration with web-based (LMS) technology.
- Feature-rich bug-tracking functionality.
- Responsiveness of the company.
Return on Investment
- Streamlined the process of tracking and resolving issues during course development.
- Allowed us to easily track issues within our embedded code-exercise IDE (Codio).
- Allowed us to better integrate our Faculty/SME authors into the development process.
Alternatives Considered
Instabug and Atlassian Jira Align (formerly AgileCraft)




