> I cannot find any issues reported against the 'cli' component in Jira in your imports though. The 'cli' Jira component is tracking issues in the CLI, which is part of jenkinsci/jenkins. If this is intentional, it seems important enough to mention in the JEP.
CLI issues will be in the next test migration, kicked off later tonight. Will be here: https://github.com/timja-org/jenkins-gh-issues-poc-11-15/issues > How are you going to handle issues with both 'core' and 'remoting' components (and similar overlaps)? They will all go to the jenkins repository if they have the core component. (handled by the fact we are archiving the issues as part of the migration which prevents them showing up in searches). I'll do a bit of sweeping through the ones with multiple components that are open and see if any can be assigned better. > Is there a test import of remoting issues we could review? I was planning to do the other core components not going to the jenkins repo afterwards. There's an export that was run here though: https://github.com/timja-org/remoting-gh-issues-poc-11-15/issues (Note this will include multi component issues as the way they are excluded is by archiving them after migration) > How are you going to update the changelog YAML format, generation and rendering in jenkins.io to account for the change in issue tracker? I cannot find any related PRs https://github.com/jenkins-infra/jenkins.io/pull/8541 On Sat, 15 Nov 2025 at 18:05, 'Daniel Beck' via Jenkins Developers < [email protected]> wrote: > Thanks, the descriptions in the most recent import look a lot better. > > I cannot find any issues reported against the 'cli' component in Jira in > your imports though. The 'cli' Jira component is tracking issues in the > CLI, which is part of jenkinsci/jenkins. If this is intentional, it seems > important enough to mention in the JEP. > > Is there a test import of remoting issues we could review? > How are you going to handle issues with both 'core' and 'remoting' > components (and similar overlaps)? Does one repo take precedence, e.g., > only import into jenkinsci/jenkins, not jenkinsci/remoting? Or perhaps into > remoting, it being the more narrowly scoped repo? > > How are you going to update the changelog YAML format, generation and > rendering in jenkins.io to account for the change in issue tracker? I > cannot find any related PRs. > > CONFIDENTIALITY NOTICE: This email and any attachments contain > confidential and proprietary information of CloudBees intended only for the > named recipient(s). Unauthorized use or distribution is prohibited. If you > received this in error, please notify the sender and delete this email. > > -- > 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/CAMo7Pt%2BhdAnVD_nJaesQf9n1o4tZSs-2bAFZKB_mm51k1PU1Zw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BhdAnVD_nJaesQf9n1o4tZSs-2bAFZKB_mm51k1PU1Zw%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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bief6222-_Pe1-kjqLL0hqHFz%2BkjSTcD_xqc-yo1fLLG9g%40mail.gmail.com.
