How to track bugs during QA of a user story

[Liz Hamilton]

Let's say we have a user story comprised of 3 technical tasks for the developer and one technical task for the QA resource. Once the developer(s) has completed the 3 development technical tasks, the QA resource knows it's time to test the user story. By this point, the QA resource has already started work on his technical task by analyzing the user story and writing scripts. So, now the QA resource begins to test the user story as a whole. So, let's say that the QA resource finds 3 bugs in the user story. What is the best way to document and track those bugs?

We've considereed a few options, but none seem to be ideal. He could add comments to the appropriate technical task or tasks that are already there and drag the affected task(s) back into the 'To Do' column. The problem with this is that the QA Resource may not know which technical task to add the comment to and if the task ends up going back and forth a few times, the comments could become too hard to parse through.

Another option would be to add a new technical task under the same user story to describe the bug(s). But, will this make it difficult to track and count outstanding bugs? (We considered either using a label for these technical tasks or starting each issue with the literal 'BUG:'.)

Another option would be to enter an new issue with a type of 'Bug'. But, these would not be listed in the same swimlane as the original user story... seems like it would be difficult for the developer and the QA resource to fully understand the context of the bug.

Our ideal solution would be if Jira/Greenhopper allowed us to add a sub-task to a user story with the type 'Bug'. But, the only sub-task types that we can add areTechnical Tasks

I'm sure all development teams have tackled this situation. How do others address it? Thanks for your help!

[Nic Brough -Adaptavist-]

Not a clue, you haven't explained what you mean by "need qa file".  There's no context or information in your question to tell us what you are talking about.

[shlomit betito]

i got a task to chek some file,if the value is fail thevalue of  file "need qa" change to yes.

do you get it?

[Nic Brough -Adaptavist-]

No, there's still no context in your question.

You need to look at a file, yes, but what value?  What's "need qa" in JIRA?  Status?  Field?  Board column?

[shlomit betito]

here my task.

1. obtaining information from an Excel file external will make 10 to 10 lines of type TEST project tasks on behalf DEALPLY.
2. each task type TEST - WF process will be as described above:
a. opening
b. Testing - will feature unique screen with the following fields:
i. Test result: Pass or Fail
3. If they fail the test results will change the field to Yes Need QA.
4. Closing Process

[Nic Brough -Adaptavist-]

So,

 1. you need to run an import from excel/csv to create the 10 issues of type Test.  (I have no idea what the fragment "on behalf dealply" means)

 2. Ok, so you'll need to create a workflow for that

[shlomit betito]

workflow in the excel file that i already import?

[Nic Brough -Adaptavist-]

I don't use excel well, I don't know how to do workflows in it.