I also really want to see issues.jenkins go away, but mostly due to how slow it is. I don't think cloud is a lot better, but way less maintenance for people.
I think the big push in the past for jira was because you couldn't migrate issues between repos before in github. That got changed.. though you still need write permission in both repos, so regular users can't migrate issues - https://help.github.com/en/github/managing-your-work-on-github/transferring-an-issue-to-another-repository - so its better, but not great. Most users are randomly guessing what components to assign things to, often just using the auto complete. For example, https://issues.jenkins-ci.org/browse/JENKINS-44148 I added the core component because after digging around on the pipeline steps doc, I learned that archiveArtifact is a "core" step. Though now that I think about it, it probably means the basic pipeline steps. Its really hard to figure out which component/repo pipeline issues should go into. With github I can "watch" the entire repo, so new PRs and new issues get emailed to me. Doesn't matter if i'm the maintainer (single or multiple), or just a random user trying to help out. With jira, I'm either auto assigned the issue due to whatever component was first picked, or nothing at all. Groups of maintainers can't be notified. Un-assigned tickets don't get notified. I like many others don't want to assign it to me until I'm working on it, so someone else could take it if they wanted. I will say the cloud model of jira is super easy to make plugins for now, and I bet if we could reach out to https://marketplace.atlassian.com/apps/1213851/watch-it-for-jira-cloud?hosting=cloud&tab=overview to get some sort of open source deal. So far no solution is great for me, I'm a slight preference for github (but maybe jira cloud if auto watching can be handled), but I agree fully that consistency is good. I never really look at jira as it stands right now its such a huge mess. Gavin On Fri, Feb 7, 2020 at 10:04 AM Daniel Beck <m...@beckweb.net> wrote: > > > > On 7. Feb 2020, at 15:56, James Nord <jamestn...@gmail.com> wrote: > > > > it kills me every time I need to file an issue and try and work out > where it is to be reported and I consider myself knowledgeable about > Jenkins and it's plugins. > > I mentioned it in a previous response, but here's the link: > https://github.com/jenkins-infra/update-center2/pull/331 > > This has the potential to make this easier than ever before. > > -- > 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/D8A0D08A-14C9-4082-8262-DF45D210B4A2%40beckweb.net > . > -- 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/CAG%3D_DusfHM4OAK23Sgwh_UhY4X71sCRkh6RvG%2BRxYKc9FX4VkA%40mail.gmail.com.
