Bug in bug report template

[Aloysius]

  Hello,
unsure where else to report this.

When filing a bug on gitlab, I've noticed that if one uses spaces between brackets in the OS field (e.g.

Code: Pascal  [Select][+][-]

1. <openSUSE Tumbleweed>

), then the field will be empty in the resulting message.

[Martin_fr]

The brackets <> are supposed to be removed.

Like in the rest of the template

Code: Pascal  [Select][+][-]

1. <Please fill in>

You would not write the entire description between <> ?

[Aloysius]

The brackets <> are supposed to be removed.

Like in the rest of the template

Code: Pascal  [Select][+][-]

1. <Please fill in>

You would not write the entire description between <> ?

That's what I did. Was it wrong?

[Martin_fr]

The brackets <> are supposed to be removed.

Like in the rest of the template

Code: Pascal  [Select][+][-]

1. <Please fill in>

You would not write the entire description between <> ?

That's what I did. Was it wrong?

No its right to remove.

But you said you did replace the

<__>

with

Code: Pascal  [Select][+][-]

1. <openSUSE Tumbleweed>

So in this case you did not.

You should be able to edit your issue.

Gitlab allows various <foo> tags to control the content (like <br/> or <b></b>)

So apparently gitlab treats <openSUSE Tumbleweed> as invisible tag. (I guess, I am not a developer in the gitlab team)

[Martin_fr]

If this is to misleading, the <> can be taken off the template.

But in the end, whatever you put in there, will be marked up by gitlab. So leading spaces, leading #, ''' and various others all translate into markup.

Also, the template is meant as a guideline, so important bits are not forgotten.

E.g.

## What happens
<Please fill in>

## What did you expect
<Please fill in>

If you write "foo bar CRASHES", then it is ok to leave the "what did you expect" empty or even remove it.

The reason the section is there, is that it is not always obvious.

Like if you said "bar.foo shows a red square", we might not know what you expect: show nothing, a red circle, a blue square, two red squares ...
You may think it is obvious, but spelling it out can save the extra round of getting feedback.
So it depends on how universally obvious it really is.

In the same sense, if you report that the word "objecd" is misspelled in some comment in the source => well your OS really does not matter.