The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
Managing multiple skillsets
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.
Thanks!
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.