PR template update

Author: michalChrobot

.github/pull_request_template.md

@@ -1,21 +1,18 @@
-<!-- Replace this block with what this PR does and why. Describe what you'd like reviewers to know, how you applied the engineering principles, and any interesting tradeoffs made. Delete bullet points below that don't apply, and update the changelog section as appropriate. -->
+## Purpose of this PR
+[//]: # (
+Replace this block with what this PR does and why. Describe what you'd like reviewers to know, how you applied the engineering principles, and any interesting tradeoffs made. 
+)
 
-<!-- Add short version of the JIRA ticket to the PR title (e.g. "feat: new shiny feature [MTT-123]") -->
+### Jira ticket
+_Link to related jira ticket ([Use the smart commits](https://support.atlassian.com/bitbucket-cloud/docs/use-smart-commits/))_
 
-## Changelog
+### Changelog
+[//]: # (updated with all public facing changes  - API changes, UI/UX changes, behaviour changes, bug fixes. Remove if not relevant.)
 
 - Added: The package whose Changelog should be added to should be in the header. Delete the changelog section entirely if it's not needed.
 - Fixed: If you update multiple packages, create a new section with a new header for the other package.
 - Removed/Deprecated/Changed: Each bullet should be prefixed with Added, Fixed, Removed, Deprecated, or Changed to indicate where the entry should go.
-
-## Testing and Documentation
-
-- No tests have been added.
-- Includes unit tests.
-- Includes integration tests.
-- No documentation changes or additions were necessary.
-- Includes documentation for previously-undocumented public API entry points.
-- Includes edits to existing public API documentation.
+- Documentation: Contains significant docs changes
 
 <!--  Uncomment and mark items off with a * if this PR deprecates any API:
 ### Deprecated API
@@ -25,12 +22,41 @@
 - [ ] The users can understand why this API was removed and what they should use instead.
 -->
 
-## Backport
+### Documentation
+[//]: # (
+This section is REQUIRED and should mention what documentation changes were following the changes in this PR. 
+We should always evaluate if the changes in this PR require any documentation changes.
+)
 
-<!-- If this is a backport:
- - Add the following to the PR title: "\[Backport\] ..." .
- - Link to the original PR.
-If this needs a backport - state this here
-If a backport is not needed please provide the reason why.
-If the "Backports" section is not present it will lead to a CI test failure. 
--->
+- No documentation changes or additions were necessary.
+- Includes documentation for previously-undocumented public API entry points.
+- Includes edits to existing public API documentation.
+
+## Testing & QA
+[//]: #  (
+This section is REQUIRED and should describe how the changes were tested and how should they be tested when Playtesting for the release.
+It can range from "edge case covered by unit tests" to "manual testing required and new sample was added".
+Expectation is that PR creator does some manual testing and provides a summary of it here.)
+
+### Functional Testing
+[//]: # (If checked, List manual tests that have been performed.)
+_Manual testing :_
+- [ ] `Manual testing done`
+
+_Automated tests:_
+- [ ] `Covered by existing automated tests`
+- [ ] `Covered by new automated tests`
+
+_Does the change require QA team to:_
+
+- [ ] `Review automated tests`?
+- [ ] `Execute manual tests`?
+
+If any boxes above are checked, please add QA as a PR reviewer.
+
+## Backport
+[//]: # (
+This section is REQUIRED and should link to the PR that targets other NGO version which is either develop or develop-2.0.0 branch
+Add the following to the PR title: "\[Backport\] ..."
+If this is not needed, for example feature specific to NGOv2.X, then just mention this fact.
+)