Best Practice to create or write an issue

[Harshit7492]

Issue Title (Concise and Descriptive)

Description

A clear and concise description of the bug/feature request.

• Expected Behavior: Describe what you expect the outcome to be.
• Actual Behavior: Describe what actually happens.

---

Steps to Reproduce

Provide a list of steps to replicate the issue:

1. Step 1
2. Step 2
3. ...

---

Screenshots/Media

Include screenshots, images, or videos if applicable.

---

Environment (for Bugs)

Include details like:

• OS: (Windows, macOS, Linux, etc.)
• Browser: (Chrome, Firefox, etc.)
• Version: (e.g., v1.0.0)

---

Possible Solution

(Optional) Suggest a possible solution if you have any ideas.

---

Additional Context

Add any other information that might be useful for solving the issue.

---

Labels

• Bug/Feature/Enhancement: Indicate the nature of the issue.
• Priority: (High, Medium, Low)
• Status: (New, In Progress, Resolved)
• Area: (Backend, Frontend, Design, etc.)

[Harshit7492]

Contributors are welcome to provide any extra context, logs, or insights that might help in resolving the issue. Feel free to add information that wasn't covered in the sections above.