Loading Profile...
Where do I document an issue found related to a story? Where do I document an issue not related to a story but is NOT in production?
If I am testing a story and find an issue related to this story, where should I document this issue? Does this go into the story or is it a new bug?
Also, if I find an issue that is not an issue in production but is an issue that cannot be traced back to a story, where do I document this issue?
Also, if I find an issue that is not an issue in production but is an issue that cannot be traced back to a story, where do I document this issue?
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Lindsay, in our workflow, Features are tested when they are in the delivered state, waiting for Accept/Reject. If there's a bug in the feature, the story is rejected and the bug is given as the reason for rejection. The Owner gets a notification that the feature was rejected and they restart the story.
Once a feature has been accepted and the iteration has passed, we don't re-open the feature to reject it. Instead we create a new bug.
Any flaw that can't be addressed by Rejecting a story should be documented as a Bug, I would think.
However, all of these patterns should be adapted to your local conditions, and as long as your team agrees it doesn't matter if you're using Tracker in the same way Pivotal Labs and our clients use Tracker.
I hope that helps!
EMPLOYEE
