updated templates for issues

.github/ISSUE_TEMPLATE/-i-need-help--issue-template.md

@@ -6,23 +6,36 @@ labels: ''
 assignees: ''
 
 ---
-
+<!--
 The most important part here for us is to understand your problem. So, please give us the more details you can. We don't want to be guessing, and you want to have a response soon, so let's make good use of the time and not spend days just gathering the information we need for the diagnostic.
+-->
+
+**Deployment (required):**
+1. Deployment: <!--It is based on the default `systemd` deployment, the alternate `docker-compose` one, a custom one of your own `k8s`, `ecs`, etc? -->
+2. Versions: <!-- Versions installed of each component used. -->
+3. Tools used for reproducing the issue: <!-- For bugs related to the API consider using api-mate or specify the external application used -->
 
-Describe the deployment (required):
-1. Is is based on the default `systemd` deployment, the alternate `docker-compose` one, a custom one of your own `k8s`, `ecs`, etc?
-2. Version installed of each component used.
-3. Tool used for reproducing the issue.
 
-Describe the problem (required):
+**Describe the problem (required):**
+<!--
+A clear and concise description of what the problem is. Ex. When I do this, this is happening [...]
+-->
 
-How to reproduce it (optional):
-If you problem is related to the API, give us the step to reproduce it using api-mate.
+**To Reproduce (optional):**
+<!--
+A clear and concise description of how to reproduce the bug. If you problem is related to the API, give us the step to reproduce it using api-mate.
+-->
 
-Other references (optional):
+
+**Other references (optional):***
+<!--
 If it is related to an integration, also specify the integration and the version of the plugin or component used.
+-->
 
-Provide Logs (may be required):
+**Logs (may be required):**
+<!--
 Include the logs from the component that is failing.
+-->
+
 
-NOTE: Request that do not provide the minimal information required won't be taken in consideration and will be immediately closed.
+*NOTE: Request that do not provide the minimal information required won't be taken in consideration and will be immediately closed.*

.github/ISSUE_TEMPLATE/bug_report.md

@@ -8,32 +8,40 @@ assignees: amalrails
 ---
 
 **Describe the bug**
+<!--
 A clear and concise description of what the bug is.
+-->
 
 **To Reproduce**
-Describe the bug:
-A clear and concise description of what the bug is.
-
-Describe the deployment:
-
-1. Is is based on the default systemd deployment, the alternate docker-compose one, a custom version of it?
-2. Version installed of each component used.
-3. Tool used for reproducing the issue.
-
-For bugs related to the API consider using api-mate.
-
-Steps to reproduce the behavior:
-
+<!--
+A clear and concise description of how to reproduce the bug.
+-->
+
+***Deployment:***
+1. Deployment: <!--It is based on the default systemd deployment, the alternate docker-compose one, a custom version of it? -->
+2. Versions: <!-- installed of each component used. -->
+3. Tools used for reproducing the issue: <!-- For bugs related to the API consider using api-mate or specify the external application used -->
+
+***Steps to reproduce the behavior:***
+<!--
+A clear and concise list of steps for reproducing the bug..
+-->
 1. '...'
-2. '....'
-3. '....'
+2. '...'
+3. '...'
 4. See error
 
 **Expected behavior**
+<!--
 A clear and concise description of what you expected to happen.
+-->
 
 **Screenshots**
+<!--
 If applicable, add screenshots to help explain your problem.
+-->
 
 **Additional context**
+<!--
 Add any other context about the problem here.
+-->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -7,14 +7,22 @@ assignees: amalrails
 
 ---
 
-**Is your feature request related to a problem? Please describe.**
+**Problem to solve:**
+<!--
 A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+-->
 
-**Describe the solution you'd like**
+**Purposed solution:**
+<!--
 A clear and concise description of what you want to happen.
+-->
 
-**Describe alternatives you've considered**
+**Considered alternatives:**
+<!--
 A clear and concise description of any alternative solutions or features you've considered.
+-->
 
-**Additional context**
+**Additional context:**
+<!--
 Add any other context or screenshots about the feature request here.
+-->