Page Comparison

...

1. confirm all necessary information supplied;
2. confirm priority; and
3. clarify effort.

Helpful reading on bug definition:

https://github.com/deegree/deegree3/wiki/Bug-Report-writing-Guidelines

https://github.com/qTox/qTox/wiki/Writing-Useful-Bug-Reports

Story Completion 'Done'

1. On completion of Sub-tasks, Devs are to add to the Story / Bug the Git summary that they write when work is complete.
2. Devs initiate a PR request, and assuming their code passes all tests, the code is committed to the DEV environment and marked in Jira as 'Ready for release'.
3. The next release that takes place deploys the code to the STAGE environment.
4. PO group test functionality in STAGE, against the story (if it's passed all unit and BDD tests, this should just be a simple spot-check health test).
5. Once the next deployment takes place from STAGE to PROD, all Stories marked as 'Ready for release' in Jira will be marked as 'Done'.
6. If a Bug is raised against a Story that had previously been marked as 'Done', that Story should be marked back as 'To do' and the Bug linked to it.

...