No no no. It needs to be jenkinsci/jenkins for everything to work smoothly otherwise we don’t get all the benefits of co-locating issues and PRs
Automation can be developed in forks. Permissions are manageable either triage or comments ops where required. Attachments we just need to keep links working I don’t think the issue links thing matters much every other project manages fine On Thu, 13 Nov 2025 at 12:14, Hervé <[email protected]> wrote: > Which repository will be used for those issues? > > I propose to use a dedicated new "core-issues" repository in jenkinsci org: > - Avoid wrong references and ambiguities > - Ex of potential problem if issues in jenkinsci/jenkins repo: somewhere > in commit (for ex) a ref to #12345 issue is added, this ref might appears > in other repositories and reference that own repository issue or PR with > the same number > - Clear meaning of links (ex: jenkinsci/core-issues#12345) everywhere > - Allow fine grained permissions without mixing them with permissions > related to Core > - The core-maintainers team could be added by default > - Specific teams/users could be created/added depdending on the needs > - Allow working on potential automation related to those issues without > triggering Core builds > - Ex: workflow > - Convenient and pertinent place to store images and attachments from Jira > in the future (only linked atm) > > WDYT? > > On Saturday, 8 November 2025 at 09:08:49 UTC+1 [email protected] wrote: > >> I agree but that migration would be a lot more complex. >> I think it should be done in phases. >> >> e.g. >> * No new components on Jira >> * Migration of core components >> * Self service migration of plugins >> * Migrate existing plugins that have dual issue tracker >> * Migrate remaining components >> >> On Fri, 7 Nov 2025 at 22:31, Ullrich Hafner <[email protected]> wrote: >> > I'm not a core developer, but as a plugin developer switching core to >>> GitHub Issues would increase the burden for all of us who still use Jira. >>> It's already a problem that I can't reassign issues to components that no >>> longer exist in Jira. If we decide to move to GitHub Issues, we should >>> migrate all components to GitHub, not only the core ones. >>> >>> >>> Am 03.11.2025 um 23:26 schrieb [email protected] <[email protected]>: >>> >>> Hi, >>> >>> I would like to revisit this 3 years later. >>> >>> There are features now available that overcome many of the issues people >>> had at the time: >>> >>> - Issue dependencies >>> >>> <https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-issue-dependencies> >>> - Sub-issues >>> >>> <https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/adding-sub-issues> >>> >>> Other new features: >>> >>> - Issue types >>> >>> <https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization> >>> - Marking as a duplicate >>> >>> <https://docs.github.com/en/issues/tracking-your-work-with-issues/administering-issues/duplicating-an-issue> >>> - Closing an issue as not planned >>> >>> <https://docs.github.com/en/issues/tracking-your-work-with-issues/administering-issues/closing-an-issue> >>> - Duplicating an issue >>> >>> <https://docs.github.com/en/issues/tracking-your-work-with-issues/administering-issues/duplicating-an-issue> >>> - Triaging an issue with AI >>> >>> <https://docs.github.com/en/issues/tracking-your-work-with-issues/administering-issues/triaging-an-issue-with-ai> >>> (not >>> tested) >>> >>> 595* plugins are using GitHub issues, + most development tools like >>> plugin-pom, ATH etc >>> >>> ~80% of new plugin hosting requests use GitHub issues for tracking. >>> >>> Other large organisations have done this sort of migration: >>> >>> - Apache Maven >>> >>> <https://open-elements.com/posts/2025/08/08/jira-issue-to-github-issue-migration-in-apache-maven/> >>> - Spring >>> >>> <https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues> >>> - Swift >>> >>> <https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125> >>> >>> Thoughts? - I'm happy to update the JEP and re-run the mock migration. >>> >>> Thanks >>> Tim >>> >>> query*: >>> repository-permissions-updater/permissions [🌱 master][⏱ 2s] >>> ❯ rg --no-heading -i 'github: \*gh' | wc -l >>> 595 >>> On Wednesday, 6 July 2022 at 16:55:54 UTC+1 [email protected] wrote: >>> >>>> On Wed, Jul 6, 2022 at 12:33 AM Damien Duportal >>>> <[email protected]> wrote: >>>> > Reporting issues with due diligence is absolutely not related to >>>> GitHub or JIRA. >>>> >>>> It is not, but the difficulty and amount of effort required to write >>>> clear steps to reproduce, expected results, and actual results far >>>> exceeds the difficulty and amount of effort required to sign up for >>>> either a GitHub account or a Jira account. The latter can be done in a >>>> few minutes after Googling for the instructions, while the former >>>> often takes me an hour or more and requires original analytical >>>> reasoning. In other words, the limiting factor (bottleneck) for >>>> effective participation is not which issue tracking system is being >>>> used but rather writing a good issue report. That is why I find the >>>> "barrier to entry" argument weak: it lowers the barrier to entry in an >>>> area that is not the limiting factor, much like optimizing the >>>> performance of a rarely used method in an application does little to >>>> help the overall performance of the same application. >>>> >>> >>> -- >>> 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/858968c8-ea04-4648-b9e1-185224653f4bn%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/858968c8-ea04-4648-b9e1-185224653f4bn%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/B1A4CC0B-D74C-446A-8351-9FEE633E02EA%40gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/B1A4CC0B-D74C-446A-8351-9FEE633E02EA%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 [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/jenkinsci-dev/713e3132-2bd9-4650-b0c4-c691aca9f373n%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/713e3132-2bd9-4650-b0c4-c691aca9f373n%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/CAH-3BicqiPX3fuBqXGh2JbSv55hNvqgYvvWg%2BAYQybLC2padfw%40mail.gmail.com.
