...
If the ticket is requires a code change, create a branch in Git named after the branch (e.g. RAXA-11) and do your work in there. Be be sure to commit and push your changes often.
...
When you are finished working on a ticket, click "Request Code Review" on the ticket page. In the comments, be sure to include a short description of how the ticket was resolved, as well as the GitHub checkin ID, which can be obtained from your Git client or the GitHub website.
From Git...
Whenever committing code, mention the ticket in the commit message - So if you are working on RAXAJSS-38, the commit message would look like e.g. "RAXAJSS-38 - Controller loads up the view". After the commit, you will receive a commit id e.g. https://github.com/Raxa/Raxa-JSS/commit/dd33a040ddbf4d9ee0c9aa8adc0dd2c4a1d972aa is id for the last one I committed. Add this id as a comment to the ticket on which you are working.