You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have some manual test cases (sanity and business related) in our system, all of them are stored as issues in Jira.
When we make a release we create test run using these test cases, and few people from QA/BA team execute them.
But we are not able to find a proper way to make estimation of these test run. We need this estimation, so that we can allocate each person proper amount of test cases during release process.
I want some suggestions and ways you all are doing this.
Currently, we have no specific custom fields that can serve the purpose you need to on the Test Cases. We have the "Begin Date" and "End Date", that were designed for the Test Plans and Test Executions.
Our suggestion is to create and use a specific custom field on the Test cases, something like "Story Points" from Jira.
AIO Tests for Jira provides an option to record estimated execution effort at time of creating test cases. When test cases are added to a test cycle for execution, the cycle detail page shows the total estimated effort of the cycle which can be used to assign resources at the time of cycle execution. Sample screenshot attached.
In addition to effort details, our cycle detail page is a comprehensive view of all the execution related details - status of execution, cycle details, run details, etc. all in one space.
Here is a link to our documentation -
If you face any issues, please feel free to contact us via
Please note, I work for AIO Support.
AIO Support Author
Hi @DPKJ ,
please have a look at this extensive page that details time tracking and the different possibilities with Xray.
The easiest approach is to estimate effort at the Test Execution issue level, similarly to what you do with any issue in Jira.
I woudln't recommend estimating effort at individual test level... as you should have some level of freedom to explore the system and evaluate properly the risks.
Personal blog on testing, Agile and software development: https://sergiofreire.com
Follow me on Twitter: @darktelecom
Well it depends on how much time it takes for the test to execute.