So re surfacing this old topic now that we've merged and deployed the updated plugin site with GitHub releases and jira issues
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, 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'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.
