Processing a Jira Ticket

1. You find a Jira ticket assigned to the programmer, which is a request for a programming change.
2. Confirm that the Jira Ticket is of type ‘Coding Task’
3. Use Jira to create a branch in bitbucket. (branch)
4. In your programming environment you switch to the develop branch (checkout)
5. You pull down any changes to the application using (pull)
6. You switch to the branch you created from Jira – it will be located under remotes/origin (checkout)
7. You change your code in that branch
8. You commit that branch (commit)
9. You push that code to the server (push)
10. In bitbucket, you create a code review (Pull Request)
11. People review / comment on the code
12. Repeat steps 7-9 until all reviewers accept the Pull request
13. You (or an application administrator) will merge that code to the main branch (merge) to the develop branch.
14. In your programming environment you switch to the develop branch (checkout)
15. Pull down changes (pull) – your develop branch is now current to all merges
16. Compile program
    1. Compile program
    2. Deploy to Development website (possibly also testing
    3. Rename the compiled folder from c:\compiled to c:\compiled_ts_20200909-a-time193
    4. update the confluence Pending XXXX Release Notes document
17. Jira ticket - change status to:
    1. "In QA" if your assembling a large update containing lots of tasks
    2. "In UAT" if the customer is notified.

×