Yea I want to get the discussion restarted so a conclusion can happen. And no, was just thinking of transferring tickets between plugins that do GitHub issues. And the triaging issues within, but yea that's another issue with the mixed env
On Wed., Jun. 10, 2020, 1:14 a.m. Ullrich Hafner, <ullrich.haf...@gmail.com> wrote: > > Am 10.06.2020 um 01:24 schrieb 'Gavin Mogan' via Jenkins Developers < > jenkinsci-dev@googlegroups.com>: > > So re surfacing this old topic now that we've merged and deployed the > updated plugin site with GitHub releases and jira issues > > > Seems that I overlooked the PR for the new plugins site. Nice work, thanks > for that! > > My next steps is start supporting GitHub issues for plugins that uses > them. But this topic never came to a conclusion. > > If we are officially supporting GitHub issues, > > > I think this has not been decided yet... > > then I think the only remaining issue is how to move incorrectly files > issues. I think you need triage or write access to migrate an issue, so I'd > like to see a bot that has access to move to either a) everyone b) everyone > with write access to Jenkins org or c) with write to either source or > destination repo. > > My vote is b. > > > I’m not sure if I can follow: you want to have a bot that syncs Jira and > GitHub? Or is it a one-way from Jira to GitHub? > > I'd like a final conclusion and an "official response" before I clean up > the PRs for update center and plugin site API. > > > On Thu., Mar. 26, 2020, 3:28 a.m. Radosław Antoniuk, < > radek.anton...@gmail.com> wrote: > >> I used this one: https://github.com/warden/jira-issues-importer >> >> -- >> 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/CAPe2pWjopjvpX%2B_oRKZ%2BW6PCsDaJj5NpUtRnj-YdJGY0t1zrdg%40mail.gmail.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/CAG%3D_Dutik45JTvY6YznY9qs8Za6Wca%3DaL1BXiKvWaoDcW0RZcw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dutik45JTvY6YznY9qs8Za6Wca%3DaL1BXiKvWaoDcW0RZcw%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/F6588E45-6D0F-4F85-81C5-7BC83A031862%40gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/F6588E45-6D0F-4F85-81C5-7BC83A031862%40gmail.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_Dut5nQhmCcQEx%3Dh2tdqWswPBbbO5bTHrhC2v1JvrDr7Fww%40mail.gmail.com.
