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.
