Loading Profile...
Integrate QA into stories and notifications
When code is complete assign to QA, with notification, for testing to begin. Notify developer and owner when QA marks as accepted or rejected.
6
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
-
Inappropriate?Right now, when coding is done the developer has to change the requester to the QA person (me) so I am notified that the code is ready for testing.
1 person thinks
this is one of the best points
1 Comment Add a comment
This is one of the best points
-
The way I've been using it at Pivotal, is the developers finish the story, then it enters the Accept/Reject state. In our case, the product owner checks out the feature and says if it meets her standards or not. I fyou had separate QA, I'd put them in at this point to accept or reject the story/bug. This works well when there are only a handful of stories finished each day (team of 4) and the QA/PO are only one or two people. What's your situation like where you're using Tracker? -
Inappropriate?Strongly agree-- workflow improvements and sensible defaults are a big win
-
Inappropriate?I agree.
Pivotal, do you have dedicated QA staff, and if so, how do they use the tool?
2 people think
this is one of the best points
-
Inappropriate?Pivotal doesn't typically have dedicated testing, but I was a tester on a Pivotal project. When I did so, either I or the customer could accept/reject a story, but not both. In practice at that particular company I was the one to accept any bug fix, and many stories. If I wasn't confident that I could accept the story on the customer's behalf, I'd call her/him over when I was done testing.
It was manageable, but I think that being able to enable a workflow where both the tester and the customer can record that they have accepted a story would be valuable.
