When i change the user story status from READY TO QA to TESTING
Do i need to change the assignee from a Developer to a Tester ?
For us you don't have to do anything. You'll have to verify with the person who created your process and see if that is the way you are supposed to work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This comes down to best practices. For me whomever is accountable for the work to be done on an issue needs to own the issue. So in your case if the developer owned resolution of the issue and then passes it off to QA for testing then it should be reassigned to the QA person. Having said that, I rarely use this method. Rather, I will create a another task and link it to the development task or I'll create a sub task under the development task.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
we do have sub tasks for each user story assigned to to dev and test seperately which we move accordingly .. when ever developers complete their sub task , they move it to ready for qa and we move the status of our sub tasks accordingly .. but when the status of user story is concerned do we need to reassign from a developer to tester is what i am confused about .. because few say we need to but few say its not needed..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.