Slashdot Mirror

← Back to Stories (view on slashdot.org)

Ask Slashdot: How Does Your Team Track And Manage Bugs In Your Software?

Posted by EditorDavid on from the issues-with-issue-tracking dept.

Slashdot reader jb373 is a senior software engineer whose team's bug-tracking methodology is making it hard to track bugs. My team uses agile software methodologies, specifically scrum with a Kanban board, and adds all bugs we find to our Kanban board. Our Kanban board is digital and similar to Trello in many regards and we have a single list for bugs... We end up with duplicates and now have a long list to try and scroll through... Has anyone run into a similar situation or do things differently that work well for their team?
The original submission ends with one idea -- "I'm thinking about pushing for a separate bug tracking system that we pull bugs from during refinement and create Kanban cards for." But is there a better way? Leave your own experiences in the comments. How does your team track and manage bugs in your software?

4 of 189 comments (clear)

  1. Bugzilla by 110010001000 · · Score: 4, Interesting

    Bugzilla. It sucks. But that is what it is there for.

    1. Re:Bugzilla by Anonymous Coward · · Score: 5, Interesting

      But all of the other solutions suck worse.

      We use JIRA, and have about 45,000 open issues (word Atlassian uses rather than bug). The search sucks, and it's nearly impossible to find what you're looking for. At least the Bugzilla bug list page has some sort of logic even if you can't tell what it is. We do four hour bug grooming meeting each week to prioritize bugs, but that typically gets ignored and customer complaints are always what is pushed to the top. Our workflow with JIRA is so overly complicated and depends on who opened the issue, the type of issue, and other options so everyone is always confused as to how to handle workflow even though we've used it for over five years. We even hired an expensive Atlassian consultant to help, but $8k later he simply made things more complicated. Bugzilla is pretty bad, but at least you know how to use it.

    2. Re: Bugzilla by Anonymous Coward · · Score: 2, Interesting

      Same experience here with Jira! Even after three full days of training when a group of us was hired last fall, we still usually don't know what to do. The having different workflow based upon hidden fields is just confusing as hell.

  2. even more agile by senatorpjt · · Score: 4, Interesting

    I wait until some manager comes by my desk and asks me to stop whatever I'm working on and fix whatever bug someone just complained about.