chore(Github): update issue template re-direct user for jira (red-hat…

…-data-services#838)

* chore(Github): update issue template re-direct user for jira

Signed-off-by: Wen Zhou <wenzhou@redhat.com>

* Update .github/ISSUE_TEMPLATE/feature_request.md

Co-authored-by: Ajay Jaganathan <36824134+AjayJagan@users.noreply.github.com>

* Update .github/ISSUE_TEMPLATE/bug_report.md

Co-authored-by: Ajay Jaganathan <36824134+AjayJagan@users.noreply.github.com>

---------

Signed-off-by: Wen Zhou <wenzhou@redhat.com>
Co-authored-by: Ajay Jaganathan <36824134+AjayJagan@users.noreply.github.com>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,24 +1,16 @@
 ---
-name: Bug report v1
-about: Create a report to help us improve v1 operator
+name: End support for v1
+about: How To
 labels: bug, v1
 ---
 
-**Describe the bug**
-A clear and concise description of what the bug is.
+# What
 
-**To Reproduce**
-Steps to reproduce the behavior:
-1. Go to '...'
-2. Click on '....'
-3. Scroll down to '....'
-4. See error
+In the summer of 2023, a new operator, v2, was released with enhanced support for ODH. 
+For more details, please refer to the blog post: [ODH Operator v2.0 Blog]([https://opendatahub.io/blog/2023-07-24-odh-operator-v2.0-blog/)
 
-**Expected behavior**
-A clear and concise description of what you expected to happen.
+During the autumn of 2023, the project decided to end the support period for ODH operator v1. The release version v1.11.0 marks the final release for operator v1; thereafter, v2.4.0 takes over. Consequently, no new feature developments or bug fixes will be pursued for v1.
 
-**Screenshots**
-If applicable, add screenshots to help explain your problem.
+# How
 
-**Additional context**
-Add any other context about the problem here.
+We strongly recommend you switch from v1 to v2, see upgrade blog: https://opendatahub.io/docs/upgrading-open-data-hub/#upgrading-the-odh-operator-v1_upgradev

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,17 +1,43 @@
 ---
-name: Feature request
-about: Suggest an idea for this project
-labels: enhancement
+name: New way to report issue on Operator v2
+about: How To
+labels: feature, enhancement, bug, v2
 ---
 
-**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 [...]
+**Updates**
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+In the winter of 2023, we transitioned GitHub Issues to the Red Hat Jira issue board located at https://issues.redhat.com. 
+Moving forward, kindly utilize this platform for reporting any new issues.
 
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+All previous issues from GitHub have been seamlessly migrated to the issue board, accompanied by a link directing users to the corresponding old issues for follow-up.
 
-**Additional context**
-Add any other context or screenshots about the feature request here.
+**How To**
+
+- Login Jira issue board https://issues.redhat.com
+- Click "Create" on top
+- Choose: "Project 'Red Hat Openshift Data Science'"
+- Issue Type:
+  - if it is a bug, choose "Bug"
+  - if it is a new feature requirement, choose "Feature"
+  - if it is an enhancement work, choose "Task"
+- Fill in "Summary" with a clear and concise description of what the ticket is.
+- Add "Description" with detail information, see below:
+  - Describe the bug***
+    - on which branch, bug is observed:
+    - has it worked before/ in which version it starts breaking:
+    - etc
+  - Steps to reproduce the behavior if it is a "Bug" type:
+    1. Go to '...'
+    2. Click on '....'
+    3. Scroll down to '....'
+    4. See error
+  - Expected behavior: a clear and concise description of what you expect to happen.
+  - Additional context: Add any other context about the ticket here.
+- Choose: "Components/s: 'Platform'"
+- Attachment: if applicable, upload screenshots to help explain more.
+
+**Troubleshooting**
+
+- If you do not have Red Hat account, you will need to create one for the first time to log in to the Jira issue board.
+- If you are unsure about certain fields when creating an issue ticket, you can leave them blank.
+- If you encounter any blocker despite your efforts, feel free to use GitHub Issue. We will assist you in mirroring GitHub issues to the issue board. Please note that this approach may take longer than creating a Jira ticket directly in the issue board.