diff --git a/.github/ISSUE_TEMPLATE/---feature-request.md b/.github/ISSUE_TEMPLATE/---feature-request.md
new file mode 100644
index 000000000..a19d22873
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/---feature-request.md
@@ -0,0 +1,17 @@
+---
+name: "\U0001F4A1 Feature request"
+about: Suggest an idea for this project
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
diff --git a/.github/ISSUE_TEMPLATE/---getting-help.md b/.github/ISSUE_TEMPLATE/---getting-help.md
new file mode 100644
index 000000000..5427e2ab7
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/---getting-help.md
@@ -0,0 +1,15 @@
+---
+name: "🙋‍Getting Help"
+about: Join https://community.parseplatform.org
+
+---
+
+<!---
+
+**We use GitHub Issues for reporting bugs with Parse JS SDK.**
+
+If you have a code-level question, use Stack Overflow with tags `parse-platform` and `parse-javascript-sdk`
+
+If you have a non-bug question, you should join the [Parse Community's Discourse forum](https://community.parseplatform.org/c/sdk/js).
+
+--->
\ No newline at end of file
diff --git a/.github/ISSUE_TEMPLATE/---parse-js-sdk-2-0-0.md b/.github/ISSUE_TEMPLATE/---parse-js-sdk-2-0-0.md
new file mode 100644
index 000000000..3af11ece4
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/---parse-js-sdk-2-0-0.md
@@ -0,0 +1,54 @@
+---
+name: "\U0001F525 Parse SDK JS 2.0.0"
+about: Report an issue while migrating to Parse SDK JS 2.0.0
+
+---
+
+<!---
+** Use this template only if you have an issue migrating to Parse SDK JS 2.0.0 **
+
+If you have a question, ask on [Parse Community's Discourse forum](https://community.parseplatform.org/c/sdk/js)
+
+If you have a vulnerability disclosure, please follow our policy available here https://github.com/parse-community/parse-server/blob/master/SECURITY.md
+
+You may also search through existing issues before opening a new one: https://github.com/parse-community/Parse-SDK-JS/issues
+
+--- Please use this template. If you don't use this template, your issue may be closed without comment. ---
+--->
+
+# Before opening the issue please ensure that you have:
+
+- [ ] [Read the migration guide](https://github.com/parse-community/parse-server/blob/master/3.0.0.md) to parse-server 3.0.0
+- [ ] [Read the migration guide](https://github.com/parse-community/Parse-SDK-JS/blob/master/2.0.0.md) to Parse SDK JS 2.0.0
+
+### Issue Description
+
+<!--- Describe your issue in as much detail as possible. -->
+
+### Steps to reproduce
+
+<!--- Please include a detailed list of steps that reproduce the issue. Include curl commands when applicable.  --->
+
+### Expected Results
+
+<!--- What you expected to happen. --->
+
+### Actual Outcome
+
+<!--- What is happening instead. --->
+
+### Environment Setup
+
+- **Server**
+  - parse-server version (Be specific! Don't say 'latest'.) : [FILL THIS OUT]
+  - Operating System:     [FILL THIS OUT]
+  - Hardware:             [FILL THIS OUT]
+  - Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [FILL THIS OUT]
+
+- **JS SDK**
+  - JS SDK version: [FILL THIS OUT]
+  - Application? (Browser, Node, React-Native, etc): [FILL THIS OUT]
+
+### Logs/Trace
+
+<!--- Include all relevant logs. You can turn on additional logging by configuring VERBOSE=1 in your environment. --->
diff --git a/.github/ISSUE_TEMPLATE/---report-an-issue.md b/.github/ISSUE_TEMPLATE/---report-an-issue.md
new file mode 100644
index 000000000..2c08465e5
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/---report-an-issue.md
@@ -0,0 +1,49 @@
+---
+name: "\U0001F41B Report an issue"
+about: Report an issue on Parse JS SDK
+
+---
+
+<!---
+
+**We use GitHub Issues for reporting bugs with Parse JS SDK.**
+
+If you have a *question*, you should join the [Parse Community's Discourse forum](https://community.parseplatform.org/c/sdk/js).
+
+If you have a vulnerability disclosure, please follow our policy available here https://github.com/parse-community/parse-server/blob/master/SECURITY.md
+
+You may also search through existing issues before opening a new one: https://github.com/parse-community/Parse-SDK-JS/issues
+
+--- Please use this template. If you don't use this template, your issue may be closed without comment. ---
+--->
+### Issue Description
+
+<!--- Describe your issue in as much detail as possible. -->
+
+### Steps to reproduce
+
+<!--- Please include a detailed list of steps that reproduce the issue. Include curl commands when applicable.  --->
+
+### Expected Results
+
+<!--- What you expected to happen. --->
+
+### Actual Outcome
+
+<!--- What is happening instead. --->
+
+### Environment Setup
+
+- **Server**
+  - parse-server version (Be specific! Don't say 'latest'.) : [FILL THIS OUT]
+  - Operating System:     [FILL THIS OUT]
+  - Hardware:             [FILL THIS OUT]
+  - Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [FILL THIS OUT]
+
+- **JS SDK**
+  - JS SDK version: [FILL THIS OUT]
+  - Application? (Browser, Node, React-Native, etc): [FILL THIS OUT]
+
+### Logs/Trace
+
+<!--- Include all relevant logs. You can turn on additional logging by configuring VERBOSE=1 in your environment. --->