Bug Tracking Software Resources

Simply put, think of BugHerd like a bulletin board with a bunch of sticky notes organized into columns. Each column is a group of tasks. Each "sticky note" is an individual task. The way we use columns is for different stages of a project. For example: design, development, quality assurance, client approved, deployed In the above example, a task would start in the "design" column and move to the next column "development" then the next column etc. The task will follow a lifecycle through many columns until it is ready to be archived. Tasks can be assigned to team member(s) and have due dates and tags along with other meta data. All the meta data will follow the task no matter what column it is in. Tagging tasks makes it easy to filter across all the columns for an aggregate group of tasks. For example: task 1 is in "development", task 2 is in "design", task 3 is in "client approved", task 4 is in "design". Tasks 1-3 have a tag of "my sweet feature" and task 4 has a tag of "some other feature" When filtering by the tag of "my sweet feature", only tasks 1-3 will display and task 4 will be hidden. However the tasks will still remain in their respective columns. The tagging support goes way deeper than the above example, but it is the most powerful component of bugherd.

Show More

Show Less

After a super fast install process, we use it for client websites to track bugs and edits needed. On the back end we triage the bug submissions into an appropriate priority, assign them to either the developer, content team, or designer depending on the nature of the bug. It's easy, and if I'm honest, quite fun!

Show More

Show Less