Add issue templates

.github/ISSUE_TEMPLATE/1_ask-a-question.md

@@ -0,0 +1,10 @@
+---
+name: Ask a question
+about: Use this template for everything that is not a bug or feature request
+title: ''
+labels: help wanted, question
+assignees: ''
+
+---
+
+

.github/ISSUE_TEMPLATE/2_bug-or-performance-issue-report.md

@@ -0,0 +1,26 @@
+---
+name: Bug or performance issue report
+about: Create a report to help us improve oneDPL
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug or performance issue is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+The following information might be useful: 
+ - CMake command: [e.g.cmake -DCMAKE_CXX_COMPILER=icpx -DCMAKE_BUILD_TYPE=release -DONEDPL_PAR_BACKEND=tbb]
+- oneDPL version: [e.g. 2022.6.0 or 224acf7423ded15d34b53429d99248c3d308b685]
+Report oneDPL version and githash. If it is a regression, report githash for the last known good revision.
+ - Compiler: [e.g. Intel(R) oneAPI DPC++/C++ Compiler 2023.1.0 (2023.1.0.20230320)]
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/3_feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for oneDPL
+title: ''
+labels: feature_request
+assignees: ''
+
+---
+
+**Summary**
+A clear and concise description of the request. 
+
+**Problem statement**
+Describe the problem you are trying to solve.
+
+**Preferred solution**
+Document your thoughts on what solution may look like.
+
+**Additional context**
+Add any other context about the feature request here.

.github/ISSUE_TEMPLATE/4_documentation_change.md

@@ -0,0 +1,21 @@
+---
+name: Documentation change request
+about: Report documentation issue or request documentation changes
+title: ''
+labels: documentation
+assignees: ''
+
+---
+
+**Summary**
+Include a short summary of the issue or request. 
+See the sections below
+for factors important for a documentation
+issue.
+
+**URLs**
+Include pointers to pages that are impacted.
+
+**Additional details**
+Provide a detailed description of the expected changes in documentation
+and suggestions you have.