> On 2. Feb 2020, at 12:13, Tim Jacomb <timjaco...@gmail.com> wrote:
>
> • 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.
At least you have the option to. I use several Jira dashboards optimized for
various tasks, and dread having to replace them with bookmarks to
gitHub.com/issues
> 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.
This seems reasonable. If they don't want a component in Jira, they don't get
one.
>
> 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.
"Cool, where do I find that?"
--
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/3FC000E7-0D66-441D-A1B6-DCE8394CEF9C%40beckweb.net.
