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 development team uses Jira to track their work. Developers are expected to add estimates to most tickets. However development time is only part of the overall time to close tickets - QA time is equally important, and in many cases may be much longer than development time. We would like a way to estimate development and testing time separately rather than chucking it all into a single bucket. Logging time should be separate so we can track dev vs QA time separately and easily.
Nope, the parent company got rid of the team before I got an answer. Still curious though!
A simple way to separate QA v dev tasks/ estimates is to use labels and query. The sub-tasks would need to be separate for dev and QA for this to work. Build a dashboard to consume the query data and present based on dev label and qa label.
We thought about this approach and ruled it out long ago.
The first problem is this would double our ticket set. The second problem is that someone would have to create EVERY ticket for testing. The third problem is we have dev estimates on subtasks, so then we would need additional subtasks to pair with the existing dev subtasks, which would make management EXTREMELY painful.
So the more I see how Jira is used (in an Agile, and particularly Scrum manner) the more uncomfortable I am with the number of tickets that get generated. One little feature could have 10 or more tickets associated with it, stories, tests, etc. Aie dios mio.