The big problem with GitHub issues is when a bug involves multiple components, or is filed against the wrong component. If you filed an issue in the wrong component, what would you expect the maintainers of that component to do? I don't think it should be on them to find the right component, so the issue just gets closer and possibly not seen by the correct people? I definitely prefer GitHub issues, but we need to address some issues like I describe above.
On Wed, Jun 10, 2020, 19:49 Brian Thompson <br...@hashvault.io> wrote: > I agree. I'd love to see Jenkins migrate from Jira to GH. As a user, if > I want to submit an issue to Jenkins, it's a bit cumbersome to create an > additional account for Atlassian just so that I can create a ticket. > However, it's highly likely that I already have a GH account and have even > browsed the codebase a bit or cloned the repo myself from GH. So having > the issues right where I am makes my life easier. > > On Wed, Jun 10, 2020 at 7:57 PM 'Gavin Mogan' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> wrote: > >> personally, as someone who replies to emails/tickets on my phone a lot, >> I'd love to see everything migrated from self hosted jira to github, and >> have one less item that the infra team needs to manage. Plus easier for >> people to report bugs since they don't need to make an ldap account first >> >> On Wed, Jun 10, 2020 at 7:06 AM Radosław Antoniuk < >> radek.anton...@gmail.com> wrote: >> >>> Am 10.06.2020 um 11:47 schrieb Radosław Antoniuk < >>>> radek.anton...@gmail.com>: >>>> >>>> Not sure I got the question right, but IMO it's each plugin's >>>> maintainer responsibility to transfer the issues from Jira to GH (with a >>>> pre-prepared solution I mentioned long ago). >>>> >>>> >>>> I think we are still one step before: should we as project allow a >>>> diversity for issue tracking or should all maintainers use Jira? Until we >>>> have no such decision we should not discuss on how to actually do a >>>> migration. >>>> >>>> >>> From standarisation and a common approach standpoint, forcing all >>> plugins to use Jira would be reasonable if not for: >>> - stability problems >>> - maintenance problems (it is not updated frequently enough imo) >>> - lack of common process (I don't like for instance that we cannot use >>> fixVersion in the workflow) >>> >>> All of those could be probably addressed but OTOH, we are also too late >>> with forcing to use Jira as a lot of plugins are already using GH issues >>> and frankly as we discsussed before, I concur with GH Issues being closer >>> to code/repository and easier for maintainers. >>> So, if each repository/plugin has it's own maintainer and noone from the >>> umbrella organisation, then it should be up to the plugin maintainers to >>> decide what they use - and we already see the tendency here. >>> >>> -- >>> 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/CAPe2pWgd9JNaTuy%3DAPsojvGKp9%3Da0zS4cE7LSN0dq%2BEizzRHBQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPe2pWgd9JNaTuy%3DAPsojvGKp9%3Da0zS4cE7LSN0dq%2BEizzRHBQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> 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/CAG%3D_Dus4DK%3DiaKZnR6gKGg4Avw1cgm%3D%2Be2gLT4LnC%3DrFbN46eg%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dus4DK%3DiaKZnR6gKGg4Avw1cgm%3D%2Be2gLT4LnC%3DrFbN46eg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Best regards, > > Brian > > -- > 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/CAHY5bT_R%3DMUhFuSjQTMcLiK%2B46tnLXKx%3DV8i40TRC-%2BncRJi%3Dw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAHY5bT_R%3DMUhFuSjQTMcLiK%2B46tnLXKx%3DV8i40TRC-%2BncRJi%3Dw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CAPiUgVcTDfyEktC3N0AVBy_mOMU6U86UkWHD6SvkCCcbQ8KS%3DQ%40mail.gmail.com.
