...
- The REPORTER of a story is responsible for providing criteria for CLOSing a story. For code implementation stories, this includes provision of a test.
- Once the story has been evaluatued to be worked, it is moved from the RECEIVED state to the OPEN state.
- The ASSIGNEE of a story STARTs WORK on the story.
- The ASSIGNEE of a story STARTs REVIEW of the story when the work is completed.
- When putting the ticket into REVIEW, a link to the GitHub pull-request should also be included in the ticket
- Note, the ASSIGNEE should STOP WORK on a story if they are temporarily changing focus to a different task.
- The REPORTER (and/or the Tech Lead) reviews/tests the finished code. Then either CLOSEs or REOPENs the story depending on the outcome of the reivewreview.
- Once a story is CLOSED, the Tech Lead (or delegate thereof) merges the code into the codebase.
...
- Start work on the ticket in JIRA
- Create an issue branch in your local git
- When you believe the ticket is complete, push the issue branch to github
- Send a pull request to master linking the JIRA ticket in the description
- Link the JIRA ticket to the pull request or commit
- Link the pull request to the JIRA ticket
- Move the JIRA ticket to IN REVIEW
- The reporter should review the change and, if it appears to be complete (including at minimum Integration and Unit Test coverage) move the ticket into CLOSED.
- The reporter should delete the issue branch in github
- The PM or Tech Lead should evaluate the demo and Accept/Reject the ticket