Related: https://groups.google.com/g/jenkinsci-dev/c/GUFCfBM1j_4
On Sat, 7 Dec 2024 at 18:53, Nikolas Falco <[email protected]> wrote: > Thanks Mark! > > I had also open a PR at > https://github.com/jenkins-infra/repository-permissions-updater/pull/4215 > > Il giorno venerdì 6 dicembre 2024 alle 16:42:48 UTC+1 Mark Waite ha > scritto: > >> On Friday, December 6, 2024 at 5:09:30 AM UTC-7 [email protected] >> wrote: >> >> Hi developers, >> As a new maintainer of bitbucket-branch-source-plugin I found myself with >> a lot of open issues to manage, this might be normal. What doesn't seem >> normal to me, is having two different issue trackers. >> >> >> Thanks for asking. I have a similar problem in one or more plugins that >> I've adopted. >> >> >> When I became maintainer there were about 100 issues on gibhub and more >> than 100 on JIRA. Now, the effort I'm spending to match issues on github -> >> JIRA and vice versa, collecting comments, use cases, steps to reproduce the >> problem... is way too much. >> I had a look in this group to see what the decision was for the default >> issue tracker, but from what I read in a couple of threads it's that the >> decision was never made but only discussed. >> >> >> The decision remains with the plugin maintainer. >> >> >> Since most of the core plugins are on JIRA and other plugins I'm the >> mantainer are on JIRA and, my preference is JIRA because of the workflow, >> notifications are not mixed with CD tasks notifications, it's easy to >> switch components, automatic assenee etc etc... all without losing history. >> I am here to ask you if the maintainer is able to freeze one of the issue >> trackers as documented on >> https://github.com/jenkins-infra/repository-permissions-updater?tab=readme-ov-file#managing-issue-trackers >> with the report attribute set to false. >> >> >> That is allowed as far as I understand it. >> >> >> Then I would announce the choose in the README.MD place in the plugin >> repository and, after all issues are resolved or manually migrated to JIRA >> (if not already present from another reported), finally remove the issue >> tab. >> >> >> That's the same transition that I'm likely to make on a few of the >> plugins that I maintain, because I prefer Jira for reasons that are similar >> to yours. >> >> 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 [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/jenkinsci-dev/93dad35f-b498-43be-b624-7f40cc6288e2n%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/93dad35f-b498-43be-b624-7f40cc6288e2n%40googlegroups.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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAE1M8%2B8aPVMi5Dv%3DZd3dJo1RUJaBFu0eaP7_eN%3Dd%3D9K_aQxRZA%40mail.gmail.com.
