Hi Tim > That thread is nearly 2 years old and the new GitHub projects and issues have come a long way in that time.
Whilst the started was old, the thread history is not and it it it has comments from Basil within the last month that *seem *relevant today. Will leave that to Basil to comment on (I am surprised given his last comment was a day before this thread was started that there has been no follow-up (even if it was a "my concerns are all addressed now"). https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/mqtV7K8uAAAJ Regards /James On Monday, June 13, 2022 at 2:55:03 PM UTC+1 timja...@gmail.com wrote: > Hi James > > That thread is nearly 2 years old and the new GitHub projects and issues > have come a long way in that time. > > To demonstrate some of what this could look like I did a POC migration > based on the INFRA one: > https://github.com/timja/jenkins-gh-issues-poc/issues > > I recreated 2 dashboards that we currently use in Jira: > > UX: > https://github.com/users/timja/projects/3/views/1 > > Core maintainers: > https://github.com/users/timja/projects/4/views/3 > > There's a tool you can use to subscribe to labels in GitHub like with Jira > (not built-in but hopefully one day): > https://github.com/orgs/github-community/discussions/16645 > > There's some sorting limitations which means I couldn't fully re-create > the core maintainers dashboard unfortunately: > https://github.com/github-community/community/discussions/8518 > > ---- > > We can certainly enhance our Jira setup but I don't see it being as smooth > and nicely integrated as GitHub is. > The barrier to entry on Jira is a lot higher than on GitHub, many people > struggle to report issues. > > I have started writing a draft JEP to put some more words together but > interested in any feedback on the above. > (I'm aware EPIC links are not included in the export, I plan to fix that) > (Web links exporting doesn't work unfortunately > https://jira.atlassian.com/browse/JRASERVER-44537) > > Thanks > Tim > > On Mon, 13 Jun 2022 at 10:19, 'jn...@cloudbees.com' via Jenkins > Developers <jenkin...@googlegroups.com> wrote: > >> https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/mqtV7K8uAAAJ >> would report there is the opposite. >> >> Whilst Jira is a PITA, GitHub issues for me has more drawbacks. >> >> We seem to be missing some improvements to Jira that would make it much >> nicer day to day, >> e.g. >> https://confluence.atlassian.com/jirasoftwareserver/configuring-development-tools-938845350.html >> >> >> /James >> On Monday, May 23, 2022 at 9:25:10 PM UTC+1 timja...@gmail.com wrote: >> >>> Hello >>> >>> Is there any interest in moving core components to GitHub issues? >>> >>> It would involve things like: >>> - Issue migration >>> - LTS backporting flow updates >>> - Documentation updates >>> - Dashboards / reporting - maybe something like >>> https://github.com/marketplace/actions/issue-dashboard >>> >>> I would be happy to prototype something / prepare a JEP if there's >>> interest. >>> >>> 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-de...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/16d883f7-0f80-4cfd-9837-5e57040a9288n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/16d883f7-0f80-4cfd-9837-5e57040a9288n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/57e56125-ee62-4a27-9662-a7c22ab62738n%40googlegroups.com.
