diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 0b750200..5fb6fd07 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -21,6 +21,17 @@ Finally, press the 'Submit new issue' button. The Core Team will evaluate and pr
 **Bug Description**
 A clear and concise description of what the bug is.
 
+**Porting from Bitshares or other Graphene forks**
+
+Corresponding issues:
+
+    - [FILL in issue1]
+    - [FILL in any other detail]
+    
+Corresponding PR:
+
+     - [fill in corresponding PR link]
+
 **Impacts**
 Describe which portion(s) of Peerplays  may be impacted by this bug. Please tick at least one box.
 - [ ] API (the application programming interface)
@@ -34,6 +45,7 @@ Describe which portion(s) of Peerplays  may be impacted by this bug. Please tick
 - [ ] UX (the User Experience)
 - [ ] Other (please add below)
 
+
 **Steps To Reproduce**
 Steps to reproduce the behavior (example outlined below):
 1. Execute API call '...'
diff --git a/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 00000000..5a6c466f
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,36 @@
+Please Note:
+
+
+1. PRs will be reviewed from oldest to newest
+2. PRs should use PR template in order to be considered for review.
+3. PRs that do not have one of the PR template completely filled out with all declarations satisfied will not be reviewed.
+
+
+### Purpose
+
+(FILL ME IN) This section describes why this PR is here. Usually it would include a reference 
+to the tracking task that it is part or all of the solution for.
+
+The Tracking issue is [Create the issue if non existent and fill in]
+
+### Declarations
+
+Check these if you believe they are true
+
+- [ ] The code base is in a better state after this PR
+- [ ] Is prepared according to the [Release Management & Versioning](https://github.com/peerplays-network/peerplays/wiki/Release-Management-&-Versioning)
+- [ ] The level of testing this PR includes is appropriate
+- [ ] All tests pass using the self-service CI/Gitlab. (TODO)
+- [ ] Changes to the API is documented
+- [ ] Testing steps for the QA team / community is shared
+
+
+### Reviewers
+
+(FILL ME IN) Reviewer 1  (If possible, assign the Reviewer for the PR)
+
+(FILL ME IN, optional) Any additional notes to reviewers or testers.
+
+### FYIs
+
+(FILL ME IN, Optional) Names of anyone else you wish to be notified of