docs: convert markdown issue templates to issue forms

[Anmol-Baranwal]

closes #1234

Changes proposed

I've added five issue forms in total and removed existing markdown templates.

I've used the existing templates as inspiration (especially the acceptance criteria).

• Documentation
• Feature Request
• Refactor Code/Feature Improvement
• Bug Report
• Other (to avoid creating blank issues) - discussion

You can see how these will preview on my fork branch. You cannot see it while creating an issue (which I've enabled) because it's in another branch and not in the main branch.

If you want to see how the final issue forms will look in general, then you can check this or this. I've contributed it myself a few months back.

Why Issue forms

• This will give you a consistent info so it will be easier to check the issue.
• Even a user with no markdown knowledge can easily fill up the form.

Note to reviewers

1. Sections that are required are marked with * Asterisk.

For instance.

2. I've also added a bit of Markdown content to improve context.

3. I've used labels of existing templates except for discussion and documentation. Let me know if any changes are necessary in that.

---

@jrobinAV
Please suggest any necessary changes, and I will make them!

[Anmol-Baranwal]

@florian-vuillemot
I've updated the placeholder as per suggestion and marked the conversation resolved.

[FabienLelaquais]

Mainly minor typographical change requests for better homogeneity.
Great work!

[Anmol-Baranwal]

@FabienLelaquais
I've made the changes and marked the suggestions as resolved.
Let me know if it needs any other changes!

[jrobinAV]

Thank you @Anmol-Baranwal for your help.

[Anmol-Baranwal]

Hi Team, if everything is okay, please review and merge this PR.

[jrobinAV]

The two other reviewers are currently on vacation. They should be back in a couple of days. I am waiting for a second approval, and once it's ok, I'll merge it.

Thank you again.

[Anmol-Baranwal]

Hi Team!
Sorry for disturbing you during your vacation time. Please feel free to reply whenever you're available.

One of the tests failed due to a spelling error in documentation. Should I correct it, even though it will dismiss the reviews?

Let me know your decision. I'm unsure about the issue with the other one.

Have a great day!

[jrobinAV]

Hello,

Oh, right. If you can fix it, that would be great. Thank you.

[Anmol-Baranwal]

@jrobinAV
I kind of missed it.

Anyway, I have updated it with the documentation label present in the repo.

I hope this works!

Let me know if you want me to fix anything else or if any test is failing.

[florian-vuillemot]

Good job thanks!

[FabienLelaquais]

Looks really good! Thanks!!