Skip to end of metadata
Go to start of metadata
Process for using JIRA
- 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 review.
- Once a story is CLOSED, the Tech Lead (or delegate thereof) merges the code into the codebase.
- Jonathan requests the Glacier Mock story. It goes into the RECEIVED state. It has no assignee. It has no acceptance criteria.
- At the sprint planning meeting, we assign acceptance criteria and move the story to the OPEN statue. The story has no assignee to do the work.
- If the story goes into the current sprint, it may not have an assignee (Don't assign assignee to stories outside sprints!).
- At the next daily scrum, Chris decides to work on this story. He STARTs WORK on the story, and makes himself the assignee.
- 3 hours later, Chris is done with the work, makes a pull request, and moves the ticket to IN REVIEW.
- Jonathan (the reporter) reviews the pull request (runs tests, etc.). When Jonathan thinks the ticket is complete, he accepts the pull request and moves the ticket to CLOSED.
- If the work is subsequently revealed to be incomplete, the Tech Lead REOPENs the story.
- Stories that have been accepted are moved to the Backlog.
- Stories that have been started must be moved to a sprint. Stories are finished and delivered in sprints.
Process for implementing a fix or feature
- 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