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
In our application workflow, we have two distinct phases - development and QA testing. I currently have a single project in JIRA, which works great for a developer - tracking their hours estimated versus actual, all the usual good project management stuff. However, while development is going on, I also have QA Analysts booking time to script out their tests, and ultimately they will take over the issue for testing.
I don't want QA and Development hours (estimated or actual) being mingled because that makes it almost impossible to track development progress. However, I also don't like creating a "QA Subtask" for each development task because now you have two cards to move through the process.
I'm sure (I hope) I'm not the only one with this challenge - how are you managing this sort of situation with JIRA? Currently "just" JIRA cloud - open to addons if needed.