Update PR template

Author: cslzchen

PULL_REQUEST_TEMPLATE.md

@@ -1,39 +1,56 @@
-<!-- Before submit your Pull Request, make sure you picked
-     the right branch:
+[//]: # (
+    * Before submit your Pull Request, make sure you've picked the right branch and your code is up-to-date with it.
+        * For critical hot-fixes, select "master" as the target branch.
+        * For bug-fixes, improvements and new features, select "develop" as the target branch.
+        * If your PR is part of a project/team, select project/team's dedicated feature branch.
+    * If you have a JIRA ticket, prefix the ticket number [ENG-*****] to the PR title.
+)
 
-     - For hotfixes, select "master" as the target branch
-     - For new features, select "develop" as the target branch
-     - For release feature fixes, select the relevant release branch (release/X.Y.Z) as the target branch -->
+## Ticket
+
+[//]: # (Link to a JIRA ticket if available.)
+
+* [ENG-*****]()
 
 ## Purpose
 
-<!-- Describe the purpose of your changes -->
+[//]: # (Briefly describe the purpose of this PR.)
 
 ## Changes
 
-<!-- Briefly describe or list your changes  -->
+[//]: # (Briefly describe or list your changes.)
 
-## QA Notes
+## Side Effects
 
+[//]: # (Any possible side effects?)
 
-<!-- Please make verification statements inspired by your code and what your code touches.
-     - Verify
-     - Verify
-     What are the areas of risk?
-     Any concerns/considerations/questions that development raised?
--->
+## QE Notes
 
-## Documentation
+[//]: # (
+    * Any QA testing notes for QE?
+        * Make verification statements inspired by your code and what your code touches.
+        * What are the areas of risk?
+        * Any concerns/considerations/questions that development raised?
+    * If you have a JIRA ticket, make sure the ticket also contains the QE notes.
+)
 
-<!-- Does any internal or external documentation need to be updated?
-     - If the API was versioned, update the developer.osf.io changelog.
-     - If changes were made to the API, link the developer.osf.io PR here.
--->
+## CE Notes
 
-## Side Effects
-
-<!-- Any possible side effects? -->
+[//]: # (
+    * Any server configuration and deployment notes for CE?
+        * Is model migration required?
+        * Is data migration/backfill/popualation required?
+        * If there is migration, is it reversible and is there roll-back plan?
+        * Does server settings needs to be updated?
+        * If there are settings update, have you checked existing settings for affected servers with CE?
+        * Are there any deployment dependencies to other services?
+    * If you have a JIRA ticket, make sure the ticket also contains the CE notes.
+)
 
-## Ticket
+## Documentation
 
-<!-- Link to Jira ticket, if applicable e.g. https://openscience.atlassian.net/browse/OSF-1234 -->
+[//]: # (
+    * Does any internal or external documentation need to be updated?
+        * If the API was versioned, update the developer.osf.io changelog.
+        * If changes were made to the API, link the developer.osf.io PR here.
+)