AnsweredAssumed Answered

How should I handle non-critical defects on a User Story

Question asked by KevinBurfitt1356461 on Aug 19, 2014
Latest reply on Sep 2, 2014 by KevinBurfitt1356461
Just wondering what the 'correct' or standard way to handle the following is:

example:
We've got a User Story, it's been implemented, tested, 4 bugs have been raised against it.   Of those bugs, 2 are deemed to be critical bugs (by the product owner) and the story can't be accepted until they are fixed.  The other two are less important and can be left until another release to be fixed.

Currently we raise all four bugs against the story, but this leaves us with a story that has open bugs and things like "Ready to Accept" don't show the story - there's no real way to tell at a glance which ones are critical and which are not.

What is a good way to handle this ?
- Leave the less important bugs as orphans ?
- Somehow mark the critical ones (perhaps with the blocked flag? although that seems to be a misuse of it)
- Live with it ?
- Something else ?

Any feedback would be welcomed!

Outcomes