As mentioned several times before I think that using or allowing 2 different issue tracker systems for *any* Jenkins component (core and plugins) is a mess for users and developers.
> Am 23.05.2022 um 20:54 schrieb Basil Crow <m...@basilcrow.com>: > > On Thu, Apr 28, 2022 at 1:22 AM 'Daniel Beck' via Jenkins Developers > <jenkinsci-dev@googlegroups.com <mailto:jenkinsci-dev@googlegroups.com>> > wrote: > > Not part of the core deliverable, but core team repos. Projects still > > likely cross issue trackers. > > Yes. In jenkins-infra/helpdesk#2819 > <https://github.com/jenkins-infra/helpdesk/issues/2819> it was suggested that > "we could use something like core, unsorted, or something more specific that > means this is a tracking issue only for use in a larger project." Not only > does this add additional (and unwanted!) burden on project managers to create > the tracking issues, but also it does not address the regression that I > reported in jenkins-infra/helpdesk/issues/2819 (comment) > <https://github.com/jenkins-infra/helpdesk/issues/2819#issuecomment-1134989606>: > prior to the archiving of the packaging component, I could have easily moved > JENKINS-68600 <https://issues.jenkins.io/browse/JENKINS-68600> to the correct > component, but now the functionality to correct the component of a misfiled > issue is not available to me. The suggested workaround is both burdensome and > incomplete. In short, the suggested workaround is not acceptable to me. > > The migration of core components to GitHub issues was incomplete. It was > incomplete in the sense that it only established the use of GitHub for new > core component issues but did not migrate existing core component issues from > Jira to GitHub. It was incomplete because it covered core components but not > itself, breaking project management use cases. It was incomplete because it > broke the existing workflow documented in the Issue Reporting > <https://www.jenkins.io/participate/report-issue/> page in the documentation > without documenting the proposed new workflow, leading to confusion for end > users. It was incomplete because it did not describe a way to move issues > filed in an incorrect component to the correct component, breaking existing > issue triage use cases. > > Completing this migration is a formidable task. The incomplete migration is > causing problems for me as I work on issue triage and project management, and > it is causing confusion for end users who have filed packaging tickets in the > wrong place multiple times. Pending the delivery of a complete migration, > please restore the status quo and move core components back to Jira. This is > a simple action that would resolve all of the problems that I have reported > and does not preclude a complete migration from taking place in the future. > > -- > 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 > <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjpYjyzk6bhuzQZTSe6PePDRbBaN2gbgLc4%2B7BzpPVoSSw%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjpYjyzk6bhuzQZTSe6PePDRbBaN2gbgLc4%2B7BzpPVoSSw%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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/FBC7E4F7-90B7-4D36-A568-B342EF2DAE0D%40gmail.com.
