Personally once a feature/change has been made in an MR/PR, a review app can then be spun up (of if QA is a developer, they can just checkout the branch with the changes) and QA is assigned the ticket. The ticket from there has all the necessary steps on what to test. Once QA has completed their testing, one of two things can happen:
-
Everything went successful, QA moved the ticket to "QA Finished" notifying the developer, the developer then can merge the MR/PR into the targeted release branch and the ticket get's moved to "Ready for Deploy" status.
-
Changes a required/testing failed, developer is tagged, makes changes, the cycle repeats until the result is #1.
This varies person to person and team to team. Different methods work for different people. Teams are of varying sizes (sometimes the developer is the developer, QA and PM). I find this works for me personally when tracking a feature/task/changes on a project.