On Fri, Nov 7, 2025 at 10:36 AM Nikolas Falco <[email protected]> wrote:
> I agree with Ullrich: the maintainer should decide which one to use to > avoid duplications, which are difficult to track when closing issues on > GitHub or Jira—that is, which is the duplicate. Some people open issues on > both because they don't know which one the maintainer considers. > The one with the link to report on plugins.jenkins.io / the Jenkins plugin manager :) But yes, if users are used to going directly to issue trackers, it's trickier. > When I had to manage two, I ran into trouble, considering that I had > already announced which was the main one in the README.MD file, yet users > continued to open issues on GitHub. > When I finally closed the issues section on GitHub (losing the history), > life became easier. > AFAICT: * Jira to GitHub can be done by archiving the component, which prevents its use in new issues * GitHub to Jira can be done with issue template definitions (or rather, explicit lack thereof): https://github.com/daniel-beck/do-not-report -- 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/CAMo7PtKBoYcE6hOvU-6vcm%3D-FDcs1WxO%3DVCCRBvH%3Dj6nfc4ZSg%40mail.gmail.com.
