chore(issue_template): #348 update label and heading descriotion as markdown comment

Author: abhisheksr01

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,38 +1,45 @@
 ---
 name: "Bug Report"
 about: "Report a bug or unexpected behavior in the Spring Boot microservice"
-title: "[bug(scope)] - [Short description of the issue]"
+title: "bug(scope) - Short description of the issue"
 labels: "bug"
 assignees: ""
 
 ---
 
 ## Description
-A clear and concise description of what the bug is and how it manifests.
+<!-- A clear and concise description of what the bug is and how it manifests. -->
 
 ## Steps to Reproduce
+<!-- 
 1. Step 1
 2. Step 2
-3. Step 3
+3. Step 3 
+-->
 
 ## Expected Behavior
-A clear description of what you expected to happen.
+<!-- A clear description of what you expected to happen. -->
 
 ## Actual Behavior
-A clear description of what actually happened.
+<!-- A clear description of what actually happened. -->
 
 ## Screenshots/Logs
-If applicable, please attach any screenshots, logs, or error messages that may help in reproducing the issue.
+<!-- If applicable, please attach any screenshots, logs, or error messages that may help in reproducing the issue. -->
 
-### Impacted Application/Tools/Utility Version:
+## Impacted Application/Tools/Utility Version:
+
+<!-- 
 - Version: [e.g. v1.0.0]
 - Spring Boot Version: [e.g. 2.5.4]
 - Cog version
 - gradle etc
+-->
 
-### Environment:
+## Environment:
+<!-- 
 - OS: [e.g. Ubuntu 20.04]
-- Java Version: [e.g. OpenJDK 11]
+- Java Version: [e.g. OpenJDK 11] 
+-->
 
 ## Additional Information
-Any other context or details that could help to resolve the issue (e.g., specific configurations, network setup, etc.).
+<!-- Any other context or details that could help to resolve the issue (e.g., specific configurations, network setup, etc.). -->

.github/ISSUE_TEMPLATE/document_improvement.md

@@ -1,24 +1,25 @@
 ---
 name: "Documentation Improvement"
 about: "Suggest an improvement or correction to the project's documentation"
-title: "[docs(scope)] - [Short description of the documentation issue]"
+title: "docs(scope) - Short description of the documentation issue"
 labels: "documentation"
 assignees: ""
 
 ---
 
 ## Description
-Describe the issue with the current documentation or areas where improvement is needed.
+<!-- Describe the issue with the current documentation or areas where improvement is needed. -->
 
 ## Suggested Changes
-Provide the suggested changes or additions to the documentation, including code snippets if applicable.
+<!-- Provide the suggested changes or additions to the documentation, including code snippets if applicable. -->
 
-### Affected Documentation
+## Affected Documentation
 - [ ] README.md
 - [ ] API Documentation
 - [ ] Developer Guide
 - [ ] Setup Instructions
+- [ ] Contribution Guide
 - [ ] Other (please specify):
 
 ## Additional Information
-Any other context, examples, or links that may help improve the documentation.
+<!-- Any other context, examples, or links that may help improve the documentation.-->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,28 +1,29 @@
 ---
 name: "Feature Request"
 about: "Request a new feature or enhancement for the spring-boot-microservice-best-practices repository"
-title: "[feat(scope)] - [short description of the Feature or enhancement]"
+title: "feat(scope)] - short description of the Feature or enhancement"
 labels: "enhancement"
 assignees: ""
 
 ---
 
 ## Description
+<!-- 
 A clear and concise description of the feature you're requesting in this repository.
-
-This can be anything from CI tool integration, Security feature (use Security-DevSecOps label), change in the code etc.
+This can be anything from CI tool integration, Security feature (use Security-DevSecOps label), change in the code etc. 
+-->
 
 ## Use Case
-Describe the problem or use case you're trying to solve with this feature.
+<!-- Describe the problem or use case you're trying to solve with this feature. -->
 
 ## Proposed Solution
-A brief outline of how this feature could be implemented or how it would work in the application.
+<!-- A brief outline of how this feature could be implemented or how it would work in the application. -->
 
 ## Benefits
-Describe the benefits of this feature and why it should be prioritized.
+<!-- Describe the benefits of this feature and why it should be prioritized. -->
 
 ### Example:
-- Provide examples of how the feature will work or how it will be used, if possible.
+<!-- - Provide examples of how the feature will work or how it will be used, if possible. -->
 
 ## Additional Information
-Any other details, mockups, or context that may help in understanding the request.
+<!-- Any other details, mockups, or context that may help in understanding the request. -->

.github/ISSUE_TEMPLATE/security_vulnerability_report.md

@@ -1,28 +1,30 @@
 ---
 name: "Security Vulnerability Report"
 about: "Report a potential security vulnerability in the Spring Boot microservice repository"
-title: "[security(scope)] - [Brief description of the vulnerability]"
-labels: "security"
+title: "security(scope) - Brief description of the vulnerability"
+labels: "vulnerabilities"
 assignees: ""
 
 ---
 
 ## Vulnerability Description
-A clear and detailed description of the potential security vulnerability. Include any identified weaknesses, attack vectors, or issues that could compromise the system.
+<!-- A clear and detailed description of the potential security vulnerability. Include any identified weaknesses, attack vectors, or issues that could compromise the system. -->
 
 ## Steps to Reproduce
+<!-- 
 1. Step 1
 2. Step 2
 3. Step 3
+ -->
 
 ## Impact
-Describe the potential impact of the vulnerability. What could be compromised (e.g., data, system access, etc.)?
+<!-- Describe the potential impact of the vulnerability. What could be compromised (e.g., data, system access, etc.)? -->
 
 ## Suggested Mitigation or Fix
-If known, provide any suggestions for mitigating the vulnerability or fixing the issue.
+<!-- If known, provide any suggestions for mitigating the vulnerability or fixing the issue. -->
 
 ### CVSS Score (Optional):
-If you are aware of the Common Vulnerability Scoring System (CVSS) score, please include it to help assess the severity.
+<!-- If you are aware of the Common Vulnerability Scoring System (CVSS) score, please include it to help assess the severity. -->
 
 ## Additional Information
-Any additional information, screenshots, or references to external sources (e.g., CVE links, research articles) that may assist in fixing or further analyzing the issue.
+<!-- Any additional information, screenshots, or references to external sources (e.g., CVE links, research articles) that may assist in fixing or further analyzing the issue. -->