Re: Revise "Bug" template fields on Jira

['Daniel Beck' via Jenkins Developers]

On Mon, Apr 17, 2023 at 6:39 PM Mark Waite 
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 
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.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJ_DA0OHAwKp%3D5U4w4XA_ZHxQEUQQ3VjCQEj7Hodyw-1g%40mail.gmail.com.

Re: Revise "Bug" template fields on Jira

[Basil Crow]

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

+1 from me

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjqd_b%3DTbxkqEDVC3%2B0GjX%2B1o_o3of_prDqfAPLQdOM8Tg%40mail.gmail.com.

Re: Revise "Bug" template fields on Jira

[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?

> Am 17.04.2023 um 18:39 schrieb 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
> 
> 
> -- 
> 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-dev+unsubscr...@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
>  
> .

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/C07A2A84-A0FE-4199-A15A-6D9EB294A8FD%40gmail.com.

Re: Revise "Bug" template fields on Jira

[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

-- 
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-dev+unsubscr...@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.

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 
*

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7b613078-29dd-4f22-84d3-44fbe9dcfa91n%40googlegroups.com.