Hi GitHub issues use is growing in the ecosystem, many plugins are now using it,
Some benefits from my experience in using it: - Easy subscription to issues / pull requests for repositories I maintain / co-maintain - Much easier to be a co-maintainer, with JIRA only the ‘component lead’ gets notified by default, you _can_ create your own filters and subscriptions, but it’s a lot more effort and most people (including me) don’t do that. - Tight integration with SCM, issues are closed when a pull request is merged, and you can click on a commit to see what version it was released in, JIRA on the other hand is very out of sync. Some repositories that are using them: https://github.com/jenkinsci/configuration-as-code-plugin, https://github.com/jenkinsci/slack-plugin, https://github.com/jenkinsci/google-compute-engine-plugin And many more... I’ve heard that this was raised a year ago or so, and there were two reasons that it wasn’t adopted: - Delete issues support - for security fixes, GitHub now supports this - Transferring issues - now supported, but I think you need write access, may need a bot to ease this, but we can see how this goes. - Cross repository / component work - There’s now organisation level projects that can be used to group and track issues across projects https://github.com/orgs/jenkinsci/projects/3 (Plugin docs), https://github.com/orgs/jenkinsci/projects/1 (Community Bridge: Jenkins Configuration-as-Code developer tools), this doesn’t solve the issue of a bug in multiple components, there’s a few ways this could be solved, one issue for tracking it, tagging the maintainers teams in the issue, reporting it multiple times and linking the issues together (possibly the best option?). I think it makes sense to offer an option during the hosting process on which issue tracker the maintainer wants to use. Currently maintainers are able to enable GitHub issues themselves after the repo is hosted but that leaves them with a JIRA component that users who are used to Jenkins JIRA might report issues into. I would also suggest that we add some text to the Component field that says: ‘Many components use GitHub issues now, if you can’t find the component create an issue on component’s GitHub repository. Any feedback or questions? Thanks Tim -- 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/CAH-3BicygmVEFYSemjj5eLNSW5usfuK3v4MmCotWfbbgNSZ2RA%40mail.gmail.com.
