We could remove the component from Kira for the plugin. It wouldn't stop someone from opening one and assigning it to the wrong component, but people assign to the wrong component all the time anyway.
On Wed, Jun 10, 2020, 02:47 Radosław Antoniuk <radek.anton...@gmail.com> wrote: > Not sure I got the question right, but IMO it's each plugin's maintainer > responsibility to transfer the issues from Jira to GH (with a pre-prepared > solution I mentioned long ago). > The question is how to prevent opening new issues in Jira afterwards, but > this actually could be automated via a simple JQL looking for open issues > in Jira that would be auto-closed with a message: "please report on > plugin's github issues". > > -- > 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/CAPe2pWju%3DbHwSqCRUVo%3DzpgS%3DsTpEu9oorxAN_37nW_tG8QBhw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPe2pWju%3DbHwSqCRUVo%3DzpgS%3DsTpEu9oorxAN_37nW_tG8QBhw%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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdPecBxcKbUHwbh9kPSCRL6Eh3%2Ba6Z%2BoM7CabRqcSDLhA%40mail.gmail.com.
