Yes there's been some work / plans around this for a while. (~2 years) A number of issues around it here: https://github.com/jenkins-infra/helpdesk/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+keycloak
No progress on it recently though. On Mon, 27 Jun 2022 at 19:29, Richard Bywater <[email protected]> wrote: > Have been following the thread and realise it's only one of the points > mentioned but if a barrier to accessing Jira is the login, has any thought > been given to allowing GitHub credentials to be used to access Jira? (Not > sure about underlying authentication system to know how easy or hard this > would be though 😀) > > Richard. > > On Tue, 28 Jun 2022, 3:53 am Basil Crow, <[email protected]> wrote: > >> On Mon, Jun 27, 2022 at 1:15 AM Tim Jacomb <[email protected]> wrote: >> > >> > Thanks for the feedback, I've created a JEP to capture and address it. >> >> I read it, but not all of the points are addressed. >> >> > GitHub conveys a lot more information about the status of issues, pull >> requests and releases than Jira does. >> >> On the contrary, GitHub does not provide enough information about the >> status of issues, forcing label-based workarounds. For example, there >> is no dedicated field for status (e.g., "Fixed but unreleased", "Won't >> fix", "Cannot reproduce", etc) and no capability for searching by >> status across components. And there is no dedicated UI element for >> linking issues (e.g., "Caused by", "Duplicates", "Depends on", etc) >> and viewing issues by links (e.g., viewing all bugs caused by a >> particular change). There is also no ability to add custom fields >> (e.g., "Released version"). The Jira Query Language (JQL) is a >> powerful way to search for issues, and as far as I can tell there is >> no equivalent in GitHub. >> >> > Jira allows explicit relationships to be set on links. GitHub requires >> you to type 'Caused by' and 'Depends on' yourself. >> >> That is an understatement: GitHub does not support relationships to be >> set on links at all. Even if you type "Caused by" and "Depends on" >> yourself, there is no way to e.g. view all the bugs that were caused >> by a particular change for a given component. >> >> > GitHub projects can be used to group issues that are across components. >> If that project doesn't use GitHub issues then […] A tracking issue can be >> created that links to a Jira epic or query >> >> As I wrote in >> https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/uy8LVZQsAAAJ >> this suggested workaorund is burdensome and therefore unacceptable to >> me. The only solution that is not burdensome for users is for the >> entire Jenkins project to use a single issue tracker for all >> components. >> >> > Jira's mobile support is very poor, commenting doesn't work on mobile >> web >> >> Sometimes people have written things to me on GitHub that do not make >> sense, and when I ask for clarification they explain away their >> writing by saying that they were using their mobile device. I think a >> good solution to this problem is to discourage people from using >> mobile devices when interacting on issue trackers. I would prefer to >> interact with people in an environment where they can write clearly >> and deliberately and edit their writing using a keyboard before >> submitting it. >> >> > Newly opened issues are labelled with `needs-triage`. >> >> This proposed triage process, which is based on issue labels, seems >> like it will add additional barriers to new contributors. Today, >> anyone with a Jira account can triage issues, but it seems like to >> manage issue labels in the proposed system users will first need to be >> given GitHub triage permissions. >> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjriE6Xf_hLN_y_XEbyApJ39qSo0Pn%2BRB%3Da_iCH_9CB2eQ%40mail.gmail.com >> . >> > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcdVCZHntQJUwQ346gHVRprOabNaTOt7fqizze6ytoZrA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcdVCZHntQJUwQ346gHVRprOabNaTOt7fqizze6ytoZrA%40mail.gmail.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidnCx6_M%2BX_V23bVyo6VEnRWYz90CwWc4CeqJJbVaUXzQ%40mail.gmail.com.
