Bug tracking please!

I would like to be able to have my QA team track bugs against a Requirement.

It would enable better visibility into the probability of a specific feature / requirement making it in to a projected Release (or the likelihood of the release slipping) if we could quantify the number of bugs associated with it.

QA should be able to identify how they are going to test each Requirement.

Each test should have a status of passed / failed

The Requirement status is then changed based on workflow:
counts of the following: Tests to do, tests done, Bugs Found,  Bugs Resolved, Passed (all counts)
status for requirements or QA test plan: Returned to Engineering, Engineering Active, Engineering Resolved, QA Active, Passed

I would like to see counts of bugs by status at the bottom of each requirement, and tallied up to features and releases. 

I'm just now starting to use Aha!, so forgive me if this is already in the product and I missed it.

  • Guest
  • Oct 21 2014
  • Already exists
Release time frame
  • Jan 6, 2016

    Admin Response

    As described in the comments below, bug tracking can be done through Aha! today. The suggested workaround is to create new requirements for each item and prefix the requirement name with "BUG" to tell the difference between the original requirememnts and implementation issues.

  • Attach files
  • Admin
    Chris Waters commented
    October 21, 2014 21:00

    Thanks for the suggestion.

    We use Aha! ourselves to track our development process. When we are developing a new feature, and we discover bugs or improvements during the QA process, we create new requirements for each item that needs to be fixed. It is not quite as elegant as what you described, but it does allow tracking of all of the changes. One technique we use is to prefix the requirement name with "BUG: " so we can tell the difference between the original requirements and the implementation problems.