I would like to vote +1 for GitHub Issues. I tried migration via the API for jira plugin and the only thing that we would lose is the original reporter (it would be noted in the comment but not the issue creator) - I think that this can be lived with. See https://github.com/warden/jira-plugin/issues for examples (those were all automated via API).
With the fact that we're not using fixVersion field and release process/board in JIRA (I don't think we need it TBH), I think that GH Issues would be more than enough. Additionally: - we could use GH Actions for automated label management, releases etc... - the users to use GH SSO only and not create special account in Jenkins - we lose performance problems with JIRA infra - we have a single and _automated_ code-to-issue linking on code-level even -- 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/94e85849-653a-4789-92a3-d84a7ca3e2ac%40googlegroups.com.
