On Mon, May 23, 2022 at 1:25 PM Tim Jacomb <timjaco...@gmail.com> wrote: > Is there any interest in moving core components to GitHub issues?
Not from me. There is, on the other hand, an interest from me (for the reasons described in https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/mqtV7K8uAAAJ) for us to > (a) stop accepting new issues on GitHub for all core components and (b) move > any existing core component issues from GitHub to Jira. On Mon, Jun 13, 2022 at 6:55 AM Tim Jacomb <timjaco...@gmail.com> wrote: > That thread is nearly 2 years old But my recent posts in that thread are less than a month old. > the new GitHub projects and issues have come a long way in that time. Yet I still cannot mark one GitHub issue as caused by or depending on another GitHub issue, and I still cannot efficiently move a GitHub issue from the incorrect component to the correct component. > The barrier to entry on Jira is a lot higher than on GitHub, many people > struggle to report issues. I do not think the barrier to entry on Jira is prohibitively high. As others have noted, reporting issues requires a certain degree of due diligence, including writing steps to reproduce, expected results, and actual results. -- 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/CAFwNDjr6e0R-qpSm9bvcDKwmOMOHyyc_6aLaF42RwAruMQ8neA%40mail.gmail.com.
