>> 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. Reporting issues with due diligence is absolutely not related to GitHub or JIRA. Both provides mecanisms (templates, etc.) to help on this area but both can be used and abused to report weird messages. Using JIRA means "keep the same people and put an entry barrier": that is how we felt for the use case of the infra. By moving to GitHub we lost the "strictness" described by Basil (EPIC, links beetween issue with associated causality such as "blocked by", etc.). In our case, loosing this "strictness" was clearly an annoyance, but compared to the sudden participation it was clearly worth the change. As a Jenkins user, I think it took me 6 years before being able even start thinking about opening an issue. The mental energy that it consume only for "creating the account + understand that there is one project for core & ALL plugins + being able to search if an issue already exist + understanding this body syntax which is its own" (not mentioning what could go wrong along: account issue, permission issue, JIRA suddenly loosing message content" is HIGH. So most of the time, I did not even started the process otherwise I was driven crazy and unable to have the "due diligence" because it was exhausting. For the infra project, going back is not an option unless we would want to remove any willingness for people to contribute or open issues. > If we expect and even encourage that most plugins switch to GitHub for issue tracking, so that we expect Jira (Cloud) to be used mainly for core and associated components and tools (plus the `SECURITY` project), does that change the calculus? There would still be plenty of people creating an account just to report some sort of core bug (or a bug which they cannot easily map to a particular plugin), but probably not tens of thousands of them. Really smart idea! Le vendredi 1 juillet 2022 à 17:07:53 UTC+2, Jesse Glick a écrit : > On Fri, Jul 1, 2022 at 3:22 AM 'Daniel Beck' via Jenkins Developers < > jenkin...@googlegroups.com> wrote: > >> we have 130k users in Jira. While many are probably not legitimate users >> of Jira […or] haven't been logged in in years >> > > If we expect and even encourage that most plugins switch to GitHub for > issue tracking, so that we expect Jira (Cloud) to be used mainly for core > and associated components and tools (plus the `SECURITY` project), does > that change the calculus? There would still be plenty of people creating an > account just to report some sort of core bug (or a bug which they cannot > easily map to a particular plugin), but probably not tens of thousands of > them. > -- 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/4b7b8879-a262-4324-b3de-92ae3227843bn%40googlegroups.com.
