add better template for issues

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,6 +1,6 @@
 ---
 name: Bug report
-about: Create a report to help us improve
+about: Represents a problem or potential problem in Harbor
 ---
 
 If you are reporting a problem, please make sure the following information are provided:

.github/ISSUE_TEMPLATE/issue.md

@@ -1,7 +1,63 @@
 ---
 name: Issue
-about: Talk about other harbor related things
-
+about: Covers everything about the project which may require some work or investigation. It is not necessarily an issue with the code, but it creates a stating point for investigation.
 ---
+<!--
+Remember, an issue is not the place to ask questions. You can use  [Stack Overflow](https://stackoverflow.com/questions/tagged/harbor)  for that, or you may want to start a discussion in [Slack](https://cloud-native.slack.com/archives/CC1E09J6S).
+
+
+Before opening a new issue, it is highly likely that someone else asked the same question before.
+
+Please search and verify that you search in those locations for answers first:
+- [ ] https://stackoverflow.com/questions/tagged/harbor
+- [ ] https://github.com/search?q=org%3Agoharbor+YOUR-ISSUE&type=issues
+- [ ] https://cloud-native.slack.com/archives/CC1E09J6S)
+- [ ] https://goharbor.io/docs/latest/
+- [ ] https://tenforward.consulting/blog/how-to-write-a-good-bug-report
+-->
+
+# Problem Descriptions
+<!-- Describe the problem and steps to reproduce it -->
+<!-- Include as many details as possible -->
+<!-- How can the developer reproduce the problem (to see it for themselves)? -->
+<!--  Every minute you spend on crafting a good and details issue will increase your chance by 5% of getting an answer   -->
+
+
+## Actual Behavior
+<!-- Tell us what  _actually_  happened after taking the steps outlined in section one. -->
+
+## Expected Behavior
+<!-- Explain what you  _expected_  to happen after taking the steps outlined in section one. -->
+
+## Steps to Reproduce
+<!-- Provide clear steps for how you arrived at the error or issue, even if it seems obvious to you -->
+
+1. [First Step]
+2. [Second Step]
+3. [and so on...]
+
+## Environment
+<!-- In which context, or environment did the problem occur?  -->
+- Harbor Version:
+- Helm Chart Version:
+- Kubernetes/Docker Version:
+- Installation and Setup:
+
+## Additional Information
+
+<!-- Any additional information, configuration, logs or data that might be necessary to
+reproduce the issue. -->
+<!-- Are they any similar issues? -->
+
+- **Harbor config files:** <!-- You can get them by packaging `harbor.yml` and files in the same directory, including subdirectory. -->
+- **Log files:** <!-- You can get them by package the `/var/log/harbor/` . -->
+
+
+## Confirmation
+I confirm that I have looking in all the following place for answers but could not find anything related. 
 
-How can we help you?
+- [ ] https://stackoverflow.com/questions/tagged/harbor
+- [ ] https://github.com/search?q=org%3Agoharbor+YOUR-ISSUE&type=issues
+- [ ] https://cloud-native.slack.com/archives/CC1E09J6S)
+- [ ] https://goharbor.io/docs/latest/
+- [ ] https://tenforward.consulting/blog/how-to-write-a-good-bug-report