How to track and manage QA work estimates in greenhopper

As a QA Engineer I would like to be able to enter QA time separately from Development time and have the sum of the two times be displayed in the Greenhopper Dashboards.

5 answers

1 accepted

The answer is that there is no good way to estimate and then track qa time. The estimate (original) time is not rolled up - although the time remaining is - so in the planning stage it is useless. (when using sub-tasks). Creating two tickets, one for the development and one for the testing is sometimes the right answer and sometimes not. I believe this is one of the incomplete answers in the Agile process itself. While it says "everything must be tested" - the process is vague with respect to the entirety of QA and really is talking about unit testing most of the time.

Gail, all time tracked is tied to the person, and you should be able to break it out by assignee in dashboard reports, but Greenhopper roles up all time, which is how the task should be estimated. (a task is estimated for both dev and QA time, and only complete once both are finished)

0 vote

Hi Gail, You might also consider adding a subtask to the issue specifically for QA and logging time against that issue. That way if you are able to quickly tell (without having to figure out who is who by role) how much time spefically was spent on QA as opposed to development. Additionally, the time spent on a sub-task should be summed with the time spent on the parent issue for reporting purposes (if you've configured your project to do so).

Hope this helps. :-)

Alex

The answer is that there is no good way to estimate and then track qa time. The estimate (original) time is not rolled up - although the time remaining is - so in the planning stage it is useless. (when using sub-tasks). Creating two tickets, one for the development and one for the testing is sometimes the right answer and sometimes not. I believe this is one of the incomplete answers in the Agile process itself. While it says "everything must be tested" - the process is vague with respect to the entirety of QA and really is talking about unit testing most of the time.

I need to see what the workload is per developer/QA engineer. Based on Atlassian's response there is no way to do that (unless I will create one issue for qa and one for development).

 

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Posted Mar 28, 2018 in Jira Software

Can a company’s culture make or break agile adoption?

Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...

13,678 views 16 15
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you