Easier issue templates

[buhtz]

Describe the problem

The templates are to restrictive.

e.g. Feature Requests do have a problem- and solution-field which are nearly useless in the context of a feature.

Describe the solution you'd like

• no templates
• or templates with simple strings describing what you want. Bot now text fields with red wildcards.
• "screenhots" field is useless because of its location. Screenshots often better placed in context of the problem description.

Describe alternatives you've considered

No response

Screenshots

No response

Additional context

No response

[nijel]

Maybe the fields could be called differently, but we really need both of them. First is there for the user to describe what he is trying to solve (the problem), second how he would like to solve that (the solution). We really want people to think about both when filing the issue so that we have some kind of specification. Otherwise, we end up asking for that info in a follow-up questions.

[buhtz]

But the user is not dump and this is not kindergarden, except the exceptions. 😄
What I have in mind is something like this makeing the user feel more free and not patronized.

This formula like layout do help no one. It make reporters feel treated like childs and it drive contributors away.

How long do you use it? Would you really say this increase the quality of issues reported?

[nijel]

But the user is not dump and this is not kindergarden, except the exceptions. 😄

Unfortunately, we saw numerous poorly reported issues before introducing this.

We use it since 2021. Before we had free form with guidance text as you link and that caused people to leave the template text there or mess up with that somehow. With forms, the formatting is not up to the user, so it's less likely to break.

[buhtz]

Thanks for sharing your experience as a maintainer. I'll take this into account in my own projects.

[github-actions]

The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.

• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

[nijel]

This really depends on the audience. In the beginning, where most people using Weblate were experienced developers, reporting issues didn't need much guidance. These days, when most of the reports come from inexperienced users, guidance is necessary because they have no clue what info is needed in a useful bug/feature report.