Belated +1 from my side, thanks for driving this effort! On Wednesday, 5 November 2025 at 15:21:54 UTC+1 [email protected] wrote:
> I think it is a sensible idea, it would lower the barrier of entry as well > as making the approach more consistent across Jenkins (plugins and core) > > On Tuesday, 4 November 2025 at 16:32:08 UTC Tim Jacomb wrote: > >> > AFAIK, GH issues still does not have a notion of priority/severity? >> It's usually all custom per project and label-based, some projects create a >> severity/p1, severity/p2 labels, etc. (?) >> > Should we consider having some kind of standard across plugins for this? >> >> If we feel there's a need then we can yes, I haven't needed it in my >> plugins that are on GitHub issues but might be more useful when more people >> are looking at it. >> >> Maven doesn't appear to use it (except on their imported issues): >> https://github.com/apache/maven/issues?page=1 >> Kubernetes uses priority/backlog, priority/important-soon etc: >> https://github.com/kubernetes/kubernetes/labels?q=priority%2F >> Go doesn't seem to use it: https://github.com/golang/go/issues >> Rust doesn't seem to use it: https://github.com/rust-lang/rust/issues >> Spring boot doesn't seem to use it: >> https://github.com/spring-projects/spring-boot/issues >> >> It definitely doesn't seem to be in widespread use. There's an option to >> do what Maven did and import from Jira as-is with priority and then see if >> we really need it or if we feel we're missing something >> >> > I know that some folks like Mark are used to checking the newly >> reported issues on Jenkins' Jira tracker across the board. >> > Is >> https://github.com/search?q=user%3Ajenkinsci++&type=issues&ref=advsearch&state=open >> the >> best entrypoint we can have for this? >> >> For general GitHub issues yes although sorted by newest would make more >> sense than best match: >> >> https://github.com/search?q=user%3Ajenkinsci++&type=issues&ref=advsearch&state=open&s=created&o=desc >> >> For Jenkins core you would be able filter by anything supported in issues >> like: >> [image: image.png] >> >> > which looks a bit time-consuming. Is that still the best available >> system, or is there some more automated system that can be requested e.g. >> from the helpdesk? >> https://github.com/jenkins-infra/repository-permissions-updater?tab=readme-ov-file#managing-issue-trackers >> does >> not mention migration at all. >> >> Assuming the process still works smoothly it's a 5-10 minute job, but yes >> an automated process would be nice. >> >> On Tue, 4 Nov 2025 at 15:36, 'Herve Le Meur CB' via Jenkins Developers < >> [email protected]> wrote: >> >>> I should be able to automate jira-issues-importer if needed. >>> >>> To be developped in an helpdesk issue, but I imagine it could run in a >>> pipeline or as additional RPU stage, tbd >>> >>> Le mar. 4 nov. 2025, 16:16, 'Jesse Glick' via Jenkins Developers < >>> [email protected]> a écrit : >>> >>>> On a related topic, what is the current recommendation for plugin >>>> maintainers wishing to switch their component from Jira to GitHub? The >>>> last >>>> I saw was >>>> https://groups.google.com/g/jenkinsci-dev/c/g3Bn1kvoT2o/m/j8IMgO2MAQAJ >>>> pointing to https://github.com/lemeurherve/jira-issues-importer which >>>> looks a bit time-consuming. Is that still the best available system, or is >>>> there some more automated system that can be requested e.g. from the >>>> helpdesk? >>>> https://github.com/jenkins-infra/repository-permissions-updater?tab=readme-ov-file#managing-issue-trackers >>>> >>>> does not mention migration at all. >>>> >>>> CONFIDENTIALITY NOTICE: This email and any attachments contain >>>> confidential and proprietary information of CloudBees intended only for >>>> the >>>> named recipient(s). Unauthorized use or distribution is prohibited. If you >>>> received this in error, please notify the sender and delete this email. >>>> >>>> -- >>>> 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 visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr31GuD6pR4MdhtLbN%3DFYZgS2M5m0bTQ%2BaaKVnM5wJeb8w%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr31GuD6pR4MdhtLbN%3DFYZgS2M5m0bTQ%2BaaKVnM5wJeb8w%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> >>> CONFIDENTIALITY NOTICE: This email and any attachments contain >>> confidential and proprietary information of CloudBees intended only for the >>> named recipient(s). Unauthorized use or distribution is prohibited. If you >>> received this in error, please notify the sender and delete this email. >>> >>> -- >>> 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 visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAL-Lwjy6wJEPmONnv4%2B5asw9dY%3DFcW1e2JSK%3DSjM6pS8VeXMfA%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAL-Lwjy6wJEPmONnv4%2B5asw9dY%3DFcW1e2JSK%3DSjM6pS8VeXMfA%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 visit https://groups.google.com/d/msgid/jenkinsci-dev/dcc9bccd-6231-451e-9301-b3e50283945en%40googlegroups.com.
