You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Christian Lenz <ch...@gmx.net> on 2019/05/15 11:16:46 UTC
Re: JIRA Template
Hi,
as I’m being tired of JIRA tickets that are not really descriptive or only oneliner etc. I want to ping this Topic again.
So at the end, I don’t care where the users are. Jira first is english so it should be english and everyone should know that. If knowone knows they tried it in there own language. If no one has any big problems with adding a jira template for Bugs, I will create an infra ticket for Apache, to add my proposal in the next couple of days.
Cheers
Chris
On 2019/02/07 14:38:01, Christian Lenz <c....@gmx.net> wrote:
> Hey guys,>
>
> sometimes we have some tickets, where we don’t know how to handle them. Only a one liner, only Headline with a stack trace, no Version, no more Information, no Environment, not in english, etc. In case to Prevent most of them (hopefully) I created a proposal for a JIRA template for Bugs, but we can make them more generic for other types too. Or we will use different template for Bugs, improvements, Features, wishes, etc.>
>
> You can find it here: https://pastebin.com/hcx7SDUb (It is unlisted, not public)>
>
> I got the idea of the template from this repo: https://github.com/junichi11/netbeans-wordpress-plugin/issues/new>
>
> Feel free to discuss, tell me what you think or give some other hints. This will not catch all 100% but hopefully most of them and if someone will not use the template, we can close the ticket and thats it. This is not rude, because they did it by their own. It is not perfect and I think there is a better way but yeah for the first run, it should be good enough to go. If someone has more Rights for that, please add it into jira. If no one knows how to do it, I can google and will let you know then.>
>
>
> Cheers>
>
> Chris>
>
AW: Re: JIRA Template
Posted by Christian Lenz <ch...@gmx.net>.
And such a template is not new, that I want to add. Github has this functionality and a lot of project uses it. Like VS Code or other big OS projects to prevent such problems.
Von: Eric Bresie
Gesendet: Mittwoch, 15. Mai 2019 13:38
An: dev
Betreff: Re: Re: JIRA Template
Is it possible to make some Jira fields mandatory when creating a ticket? Then maybe make description, version, how to reproduce, etc. required.
Eric Bresie
Ebresie@gmail.com
> On May 15, 2019 at 6:16:46 AM CDT, Christian Lenz <ch...@gmx.net> wrote:
> Hi,
>
> as I’m being tired of JIRA tickets that are not really descriptive or only oneliner etc. I want to ping this Topic again.
> So at the end, I don’t care where the users are. Jira first is english so it should be english and everyone should know that. If knowone knows they tried it in there own language. If no one has any big problems with adding a jira template for Bugs, I will create an infra ticket for Apache, to add my proposal in the next couple of days.
>
>
> Cheers
>
> Chris
>
>
> On 2019/02/07 14:38:01, Christian Lenz <c....@gmx.net> wrote:
> > Hey guys,>
> >
> > sometimes we have some tickets, where we don’t know how to handle them. Only a one liner, only Headline with a stack trace, no Version, no more Information, no Environment, not in english, etc. In case to Prevent most of them (hopefully) I created a proposal for a JIRA template for Bugs, but we can make them more generic for other types too. Or we will use different template for Bugs, improvements, Features, wishes, etc.>
> >
> > You can find it here: https://pastebin.com/hcx7SDUb (It is unlisted, not public)>
> >
> > I got the idea of the template from this repo: https://github.com/junichi11/netbeans-wordpress-plugin/issues/new>
> >
> > Feel free to discuss, tell me what you think or give some other hints. This will not catch all 100% but hopefully most of them and if someone will not use the template, we can close the ticket and thats it. This is not rude, because they did it by their own. It is not perfect and I think there is a better way but yeah for the first run, it should be good enough to go. If someone has more Rights for that, please add it into jira. If no one knows how to do it, I can google and will let you know then.>
> >
> >
> > Cheers>
> >
> > Chris>
> >
>
>
AW: Re: JIRA Template
Posted by Christian Lenz <ch...@gmx.net>.
This makes sense yes but if you only add the stacktrace inside the description or smth like: „there was an error and I added it here“ doesn’t make sense at all.
Von: Eric Bresie
Gesendet: Mittwoch, 15. Mai 2019 13:38
An: dev
Betreff: Re: Re: JIRA Template
Is it possible to make some Jira fields mandatory when creating a ticket? Then maybe make description, version, how to reproduce, etc. required.
Eric Bresie
Ebresie@gmail.com
> On May 15, 2019 at 6:16:46 AM CDT, Christian Lenz <ch...@gmx.net> wrote:
> Hi,
>
> as I’m being tired of JIRA tickets that are not really descriptive or only oneliner etc. I want to ping this Topic again.
> So at the end, I don’t care where the users are. Jira first is english so it should be english and everyone should know that. If knowone knows they tried it in there own language. If no one has any big problems with adding a jira template for Bugs, I will create an infra ticket for Apache, to add my proposal in the next couple of days.
>
>
> Cheers
>
> Chris
>
>
> On 2019/02/07 14:38:01, Christian Lenz <c....@gmx.net> wrote:
> > Hey guys,>
> >
> > sometimes we have some tickets, where we don’t know how to handle them. Only a one liner, only Headline with a stack trace, no Version, no more Information, no Environment, not in english, etc. In case to Prevent most of them (hopefully) I created a proposal for a JIRA template for Bugs, but we can make them more generic for other types too. Or we will use different template for Bugs, improvements, Features, wishes, etc.>
> >
> > You can find it here: https://pastebin.com/hcx7SDUb (It is unlisted, not public)>
> >
> > I got the idea of the template from this repo: https://github.com/junichi11/netbeans-wordpress-plugin/issues/new>
> >
> > Feel free to discuss, tell me what you think or give some other hints. This will not catch all 100% but hopefully most of them and if someone will not use the template, we can close the ticket and thats it. This is not rude, because they did it by their own. It is not perfect and I think there is a better way but yeah for the first run, it should be good enough to go. If someone has more Rights for that, please add it into jira. If no one knows how to do it, I can google and will let you know then.>
> >
> >
> > Cheers>
> >
> > Chris>
> >
>
>
Re: Re: JIRA Template
Posted by Eric Bresie <eb...@gmail.com>.
Is it possible to make some Jira fields mandatory when creating a ticket? Then maybe make description, version, how to reproduce, etc. required.
Eric Bresie
Ebresie@gmail.com
> On May 15, 2019 at 6:16:46 AM CDT, Christian Lenz <ch...@gmx.net> wrote:
> Hi,
>
> as I’m being tired of JIRA tickets that are not really descriptive or only oneliner etc. I want to ping this Topic again.
> So at the end, I don’t care where the users are. Jira first is english so it should be english and everyone should know that. If knowone knows they tried it in there own language. If no one has any big problems with adding a jira template for Bugs, I will create an infra ticket for Apache, to add my proposal in the next couple of days.
>
>
> Cheers
>
> Chris
>
>
> On 2019/02/07 14:38:01, Christian Lenz <c....@gmx.net> wrote:
> > Hey guys,>
> >
> > sometimes we have some tickets, where we don’t know how to handle them. Only a one liner, only Headline with a stack trace, no Version, no more Information, no Environment, not in english, etc. In case to Prevent most of them (hopefully) I created a proposal for a JIRA template for Bugs, but we can make them more generic for other types too. Or we will use different template for Bugs, improvements, Features, wishes, etc.>
> >
> > You can find it here: https://pastebin.com/hcx7SDUb (It is unlisted, not public)>
> >
> > I got the idea of the template from this repo: https://github.com/junichi11/netbeans-wordpress-plugin/issues/new>
> >
> > Feel free to discuss, tell me what you think or give some other hints. This will not catch all 100% but hopefully most of them and if someone will not use the template, we can close the ticket and thats it. This is not rude, because they did it by their own. It is not perfect and I think there is a better way but yeah for the first run, it should be good enough to go. If someone has more Rights for that, please add it into jira. If no one knows how to do it, I can google and will let you know then.>
> >
> >
> > Cheers>
> >
> > Chris>
> >
>
>