Revise "Bug" template fields on Jira

[Alexander Brandes]

Hey everyone,

Commonly, when I'm triaging (core) issues, I almost always face submissions like JENKINS-71064 and JENKINS-70732.
These two figures are prime examples of how issue submissions are not supposed to look like. The list is long, and based on my observation, getting longer by day.

I don't believe it's healthy to continuously bug submitters to provide details on their setup, when they could - and are supposed to - do that during the submission form.
That's part of the issue reporting documentation, we link on the issue form, but is commonly ignored.

I would like to propose making the "Environment" and "Description" fields mandatory for "Bug" type issues on Jira, to go a bit against issue submissions without any useful information at all and stop us playing guessing games.

Best regards,

Alex

This mail is a copy of https://github.com/jenkins-infra/helpdesk/issues/3515

[Mark Waite]

On Monday, April 17, 2023 at 3:01:10 AM UTC-6 Alexander Brandes wrote:

Hey everyone,

Commonly, when I'm triaging (core) issues, I almost always face submissions like JENKINS-71064 and JENKINS-70732.
These two figures are prime examples of how issue submissions are not supposed to look like. The list is long, and based on my observation, getting longer by day.

I don't believe it's healthy to continuously bug submitters to provide details on their setup, when they could - and are supposed to - do that during the submission form.
That's part of the issue reporting documentation, we link on the issue form, but is commonly ignored.

I would like to propose making the "Environment" and "Description" fields mandatory for "Bug" type issues on Jira, to go a bit against issue submissions without any useful information at all and stop us playing guessing games.

No objection from me to making those fields mandatory, especially the description field.  I'd like the Jira experts like Basil Crow and Daniel Beck to voice their opinions.  I think that it makes sense, but they better understand the interactions between Jira components and can guide us if there is a compelling reason not to make those fields mandatory.

Mark Waite

[Ullrich Hafner]

I think it makes sense to make the description mandatory. 

I’m not sure if the same should be done for the environment property (at least not globally). Wouldn’t it make more sense to make the affected core version selectable with something like a list box?

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b0d6b0f0-4ab3-4afe-a8dc-bbd1b09e9fban%40googlegroups.com.

[Basil Crow]

On Mon, Apr 17, 2023 at 2:01 AM Alexander Brandes <mc.ca...@gmail.com> wrote:
>
> I would like to propose making the "Environment" and "Description" fields mandatory for "Bug" type issues on Jira

+1 from me

[Daniel Beck]

On Mon, Apr 17, 2023 at 6:39 PM Mark Waite <mark.ea...@gmail.com> wrote:

I'd like the Jira experts like Basil Crow and Daniel Beck to voice their opinions.

Should be doable. It looks like we'd need to copy the field configuration, mark the fields required in the copy, define a new field configuration scheme, have the Bug type associated with the field configuration that has the required fields, all others with the original, and use that scheme for JENKINS. Does that sound about right?

I don't know how Jira handles new requirements for fields in existing issues. This might result in updating existing issues being quite cumbersome.

On Mon, Apr 17, 2023 at 7:57 PM Ullrich Hafner <ullrich...@gmail.com> wrote:

Wouldn’t it make more sense to make the affected core version selectable with something like a list box?

Environment is more than core version. Also, there are _many_ core versions, most of which are irrelevant for new issues, but would need to be kept around for historical issues. If we wanted this, it would be a separate field, and would need to be updated] every week.