...
Table of Contents |
---|
Issue Types
Additions
Issue Type | Reporter | Tracks | Deliverable(s) |
---|---|---|---|
Wish / New Feature |
|
|
|
Requirements |
|
|
|
Epic |
|
|
|
Story |
|
|
|
Alterations
Issue Type | Reporter | Tracks | Deliverable(s) |
---|---|---|---|
Improvement |
|
|
|
Bug |
|
|
|
Accounting
Issue Type | Reporter | Tracks | Deliverable(s) |
---|---|---|---|
Comment |
|
|
|
Processing Request |
|
|
|
Task |
|
|
|
Sub-Task |
|
|
|
Technical Task |
|
|
|
Workflows
Addition Workflows
...
- GitHub: Pull Request(s)
- DockerHub: New Image(s) / Tag(s)
- Confluence: Documentation describing the technical aspects of how the platform fulfills the Use Case
- ???Zephyr: Test Case(s) demonstrating the use case fulfilled by the story
- TODO: discover software for writing test plans
...
- GitHub: Pull Request(s)
- DockerHub: New Image(s) / Tag(s)
- Confluence: Updated technical documentation that reflects any modifications to the platform
- ???Zephyr: Test Case(s) exercising the benefit introduced by this improvement
- TODO: discover software for writing test plans
...
- Ticket Status: Start Progress
- Developer creates a new branch with a small prototype instance containing suggested improvement(s)
- Developer weighs the pros / cons of this solution over the current one against the time it would take to fully implement and test the change
- If not desirable, the developer abandons the branch(es) containing these changes and marks the ticket as CLOSED
- If desirable, the developer completes the modifications on the branch
- Once complete, developer gathers the necessary deliverables:
- Confluence: Create documentation and/or take note of technical details
- GitHub: Create Pull Request(s)
- DockerHub: Create and push a test image tagged with the name of the corresponding git branch
- ???Zephyr: Create new / update existing test cases relating to the modifications
- Ticket Status: Review Ticket and assign to Tester
- Tester reviews / tests any deliverables
- Confluence: Review any relevant documentation or technical details
- GitHub: Review related Pull Request(s)
- DockerHub: Pull and run test image(s) against test cases
- ???Zephyr: Run any new / updated test cases relating to the modifications
- Tester merges any Pull Requests (if applicable)
- Ticket Status: Resolve Ticket and assign back to Developer
- Developer releases other deliverables themselves
- Confluence: Developer migrates any relevant documentation from Personal Space to "National Data Service" public space (if applicable)
- GitHub: Developer syncs with upstream changes (if applicable)
- git checkout master
- git pull upstream master
- git push origin master
- DockerHub: Developer builds and pushes new "latest" stable Docker images
- GitHub: Developer commits and pushes new build date upstream (if applicable)
- Ticket Status: Close Ticket
...
- GitHub: Pull Request(s)
- DockerHub: New Image(s) / Tag(s)
- Confluence: Updated technical documentation that reflects any modifications to the platform
- ???Zephyr: Updated / new Test Case(s) reflecting the expected behavior of the product
- TODO: discover software for writing test plans
...
- Ticket Status: Start Progress
- aside: consider creating a new status for "Verification" stage of Bug tickets?
- Developer reviews affected Use Case(s) and verifies behavioral divergence
- Developer examines validity and may suggest modifications to the Use Case
- Developer determines where the bug stems from in the source
- Developer devises one or more ways to address the bug in question
- Developer selects the "best" option according to their judgement given the circumstances
- Developer fixes product behavior to match expected Use Case
- Once complete, developer gathers any necessary deliverables:
- Confluence: Create documentation and/or take note of technical details
- GitHub: Create Pull Request(s)
- DockerHub: Create and push a test image tagged with the name of the corresponding git branch
- ???Zephyr: Create new / update existing test cases relating to the modifications
- Ticket Status: Review Ticket and assign to Tester
- Tester reviews / tests any deliverables
- Confluence: Review any relevant documentation or technical details
- GitHub: Review related Pull Request(s)
- DockerHub: Pull and run test image(s) against test cases
- ???Zephyr: Run any new / updated test cases relating to the modifications
- Tester merges any Pull Requests (if applicable)
- Ticket Status: Resolve Ticket and assign back to Developer
- Developer releases other deliverables themselves
- Confluence: Developer migrates any relevant documentation from Personal Space to "National Data Service" public space (if applicable)
- GitHub: Developer first syncs with upstream changes (if applicable)
- git checkout master
- git pull upstream master
- git push origin master
- DockerHub: Developer builds and pushes new "latest" stable Docker images
- GitHub: Developer commits and pushes new build date upstream (if applicable)
- Ticket Status: Close Ticket
...