Hi developers, As a new maintainer of bitbucket-branch-source-plugin I found myself with a lot of open issues to manage, this might be normal. What doesn't seem normal to me, is having two different issue trackers. When I became maintainer there were about 100 issues on gibhub and more than 100 on JIRA. Now, the effort I'm spending to match issues on github -> JIRA and vice versa, collecting comments, use cases, steps to reproduce the problem... is way too much. I had a look in this group to see what the decision was for the default issue tracker, but from what I read in a couple of threads it's that the decision was never made but only discussed. Since most of the core plugins are on JIRA and other plugins I'm the mantainer are on JIRA and, my preference is JIRA because of the workflow, notifications are not mixed with CD tasks notifications, it's easy to switch components, automatic assenee etc etc... all without losing history. I am here to ask you if the maintainer is able to freeze one of the issue trackers as documented on https://github.com/jenkins-infra/repository-permissions-updater?tab=readme-ov-file#managing-issue-trackers with the report attribute set to false. Then I would announce the choose in the README.MD place in the plugin repository and, after all issues are resolved or manually migrated to JIRA (if not already present from another reported), finally remove the issue tab.
-- 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 visit https://groups.google.com/d/msgid/jenkinsci-dev/8d1279b2-b7ef-4af5-9ff7-0a0ccb9ded3en%40googlegroups.com.
