chore(github): Update issue template to have several choices

[benoitf]

What does this PR do?

Provide a list of choices when creating issues

Enhance the templates to ask more questions when reporting a bug

What issues does this PR fix or reference?

Related to End Game #13637

Fix #13648

Change-Id: I3586957c6687dbdf4b528ccf62bd07e82b2887f1
Signed-off-by: Florent Benoit fbenoit@redhat.com

[slemeur]

I love it !

I'm wondering if we need the usability section as this might be related to enhancements?

Order, I would put:

• Question
• Bug report
• Enhancement
• Usability
• Documentation
• Task

But that's great. Thanks @benoitf !

[benoitf]

@slemeur it's because we have kind/usability label
It seems @tsmaeder introduced that label
Maybe you need to see if usability can be merged into enhancement

[benoitf]

@rkratky we can make you as default assignee as well there

Also we can add the template that you would want for documentation items.

[l0rd]

Very nice @benoitf . +1 to remove usability. I would even make it simpler and remove:

• documentation: for me it's an area or component, not a kind. For instance it makes perfectly sense to have kind/enhancement with area/docs
• task: I always struggle with the difference between a task and an enhancement

[benoitf]

ok so consensus for now is to remove usability (and then remove the label I think ?)

I agree with you that kind/docs is more area/docs now that docs issues are also there

About task, in description (that is in the label) is that it's more technical-debt, something that you should do but it may not be an enhancement at all.
Usage of kind/task is quite widely spread with almost 200 opened issues with that label https://github.com/eclipse/che/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Ftask
If most of people are thinking that task can be merged into enhancement we could reduce the numbers of kind/ item as well

I will not do changes on the PR until beginning of next week to let people comment and grab other feedback.

[sunix]

I will not do changes on the PR until beginning of next week to let people comment and grab other feedback.

Ok, my feedback is that to make some decision like what we take for the release, we take some criteria like:

• "We do not add more new features for GA" --> enhancement (but should be new feature ?)
• "We have to update the README to include a contribution section" --> task or doc
• "We have to update the jenkins job to include the ability to build PR branches" --> task
• "this flow is ok but it would be nicer to have the button on the top" --> usability .. not a new feature, not really a bug, UX.

Finally would enhancement (that would englobe several kinds of issue) help us in taking decisions and moving forward ? I don't think so.

[benoitf]

@sunix I think you can address some of your remarks with naming convention in your commits
https://www.conventionalcommits.org/

[benoitf]

ci-build

[benoitf]

@slemeur @l0rd PR updated

[slemeur]

LGTM

[sunix]

@sunix I think you can address some of your remarks with naming convention in your commits
https://www.conventionalcommits.org/

yes but before coding (when filling the issue) and while planning (choosing which issue to do next), how can I address that ?

[benoitf]

you can still give issue/PR title with this convention (look at this PR title)