Create Separate Issue Templates for Different Issue Types

[SrijaVuppala295]

Feature Description

To streamline the issue reporting process and ensure clarity in the project, we propose the creation of distinct issue templates for various categories. This will help contributors easily select the relevant template and provide the necessary details.

1. Frontend Issue Template

• Description: This template is for any issues related to the frontend UI/UX, including bugs, design improvements, or new features.
• Fields:
  • Issue Summary
  • Steps to Reproduce (for bugs)
  • Expected Behavior
  • Screenshots (if applicable)
  • Additional Notes

2. Backend Issue Template

• Description: This template is for backend-related issues, such as API bugs, database queries, or server-side logic problems.
• Fields:
  • Issue Summary
  • Steps to Reproduce (for bugs)
  • Expected Behavior
  • Log Files (if applicable)
  • Database or API-related details

3. Documentation Update Template

• Description: This template is for reporting issues or suggesting updates to project documentation.
• Fields:
  • Section of Documentation
  • Suggested Changes
  • Reason for Update
  • Screenshots or Examples (if applicable)

4. Pull Request Template

• Description: This template helps contributors fill out necessary information for their pull request, ensuring that all important details are provided for review.
• Fields:
  • Description of Changes
  • Related Issue(s)
  • Testing Details
  • Any Additional Notes

Creating these templates will help in better organizing issues and provide clarity on what information needs to be included for each type, improving project management and collaboration.