How best can QA velocity be tracked?

[Somtochukwu Ofodum]

If there is no timeline and assignment to a QA Engineer when issues are moved to QA, how best can their work be tracked?

[Karolina Wons_SaaSJet]

Hello @Somtochukwu Ofodum 

Welcome to the comunity.

As for me, the best way is to assign tickets to a particular developer and then track the total time the task has spent in all statuses using some tools from the Atlassian Marketplace. 

As an alternative, you can try Time in Status for Jira Cloud developed by my team. It provides such functionality. 

Are you ok with using third-party add-ons?

Hope you find it helpful

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

If you're doing your QA in a separate team, you should be looking at how that team is doing their sprints.  The best way to implement this (not agile) structure, you should have a board for the developers and a board for the QA team, with both boards having the right timeline and assignments set properly to represent what your process and ownerships are.

[Chris Boys]

@Somtochukwu Ofodum,

Depending on how big your QA team is, I agree with @Nic Brough -Adaptavist-. 

If you're like us, we have QA integrated within our flow, and have a separate column in our board prior to 'Done'.    As @Karolina Wons_SaaSJet suggests, you can then track the time issues spend in the QA status, relative to all other status' that your flow includes and see how quickly issues are being moved through QA.

You can observe your team's Time In Status in Umano's Team Performance Summary, along with 20 other markers of your team's design, build, review and engagement practices.

Let me know if I can help further.  Go well!

Chris