Dedicated issue templates for different parts of inlang

[ivanhofer]

Problem

Opening an issue currently is done through a big textarea with some prefilled content. Some people have troubles opening the issue with the correct formatting. And they probably also don't know what kind of information we need in order to resolve the issue. Which means we have to write a comment and wait for them to respond, which could take another day until we can start investigating.

Solution

GitHub offers a way to retrieve information in a structured way with issue templates.
You can already find an example for our bug reports here.

Each part (IDE, SDK, plugins, CLI, Editor, ...) could create its own issue template and define important fields there. e.g. the SvelteKit version for the SDK or the browser version for the Editor etc.. This could result into the situation, where we already have all information we need in order to start fixing the issue, without another loop of interaction.
Another great benefit would be to be able to already define the labels and assign the persion in charge to that issue, resulting in faster awareness of an incoming issue.

What do you think?

[samuelstroschein]

Does GitHub support dropdowns to select which app?

• creating a bug template for every app is overwhelming
• having one bug template which adapts to the app via a dropdown or similar seems better

[ivanhofer]

I'm not sure if you can render conditional forms, but I agree this would be ideal.

[ivanhofer]

Conditional forms are not possible.

Is it so bad to have a few more options?

• feature suggestion (could link to discussions)
• bug: plugin(s)
• bug: sdk
• bug: cli
• bug: ide-extension
• bug: editor
• bug: general

Maybe editor and something else don't need a dedicated issue template with custom fields and the "general" template can be used.

[samuelstroschein]

Is it so bad to have a few more options?

I assume that people will ignore the options and choose something random. You can try though

[ivanhofer]

Let's try