This should do what you are after: https://github.com/jenkinsci/jenkins/issues?q=is%3Aissue%20state%3Aopen%20in%3Atitle%20RSS%20Feeds%20Ought%20to%20Accept%20Credentials
is:issue in:title RSS Feeds Ought to Accept Credentials On Thu, 27 Nov 2025 at 18:19, 'James Nord' via Jenkins Developers < [email protected]> wrote: > > https://support.atlassian.com/jira/kb/how-to-make-jira-issues-read-only-using-workflow-properties/ > perhaps? > > On Thursday, November 27, 2025 at 6:15:06 PM UTC James Nord wrote: > >> Is there a way to lock the migrated issues without archiving them? >> >> e.g. >> >> https://issues.jenkins.io/issues/?jql=summary%20~%20%22RSS%20Feeds%20Ought%20to%20Accept%20Credentials%22%20and%20project%20%3D%20JENKINS >> produces zero hits. >> yet https://github.com/jenkinsci/jenkins/issues/19594 >> >> This is a pain as GH search searches the entire ticket (including the >> description) and I want to narrow the focus to just search the summary. (GH >> is currently giving me hundreds of results to trwal thorugh when I should >> be able to limit it to < 10). >> Or is there some other GH search foo to only search the title of an issue? >> >> (and yes this only would work for old issues, but this is an old issue I >> am looking for). >> >> I am also concerned that the lack of decent search is likely to cause >> more duplicates to be filed, but then that is dependant on people searching >> before filing issues which may not actually happen, and this ship has >> sailed. >> >> /James >> >> >> On Tuesday, November 25, 2025 at 8:33:14 PM UTC [email protected] wrote: >> >>> The core / cli component migration is complete now. >>> >>> Mapping files from the migration are here: >>> https://github.com/jenkins-infra/helpdesk/issues/4870#issuecomment-3577410722 >>> >>> Remaining work: >>> * Send notification to everyone who participated / watched a migrated >>> issue >>> * Migration other core components, e.g. remoting. >>> >>> Jira notifications have been re-enabled and the banner updated. >>> >>> >>> >>> On Tue, 25 Nov 2025 at 08:10, Tim Jacomb <[email protected]> wrote: >>> >>>> The migration is close to done, all issues are imported. >>>> >>>> I've paused updating the Jira issues as notifications are going out, >>>> which wasn't happening when we were testing. >>>> >>>> We had planned to just send one bulk email. >>>> >>>> On Mon, 24 Nov 2025 at 07:48, Tim Jacomb <[email protected]> wrote: >>>> >>>>> The migration to GitHub has begun: see >>>>> https://github.com/jenkinsci/jenkins/issues >>>>> >>>>> Tracking issue: https://github.com/jenkins-infra/helpdesk/issues/4870 >>>>> >>>>> On Sun, 23 Nov 2025 at 14:41, Tim Jacomb <[email protected]> wrote: >>>>> >>>>>> Done, see example >>>>>> https://github.com/timja-org/jenkins-gh-issues-poc-11-23/issues/4856 >>>>>> >>>>>> On Sat, 22 Nov 2025 at 13:35, Jenkins Developers < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Thanks very much. Could the migration tooling be extended to add >>>>>>> the 'good first issue' label on migrated issues that have the Jira label >>>>>>> 'newbie-friendly'? We've used that to identify issues that are well >>>>>>> suited >>>>>>> to new contributors. >>>>>>> >>>>>>> I also understand if that is not feasible. It can be done after the >>>>>>> migration if it doesn't fit into the migration schedule. >>>>>>> >>>>>>> Mark Waite >>>>>>> >>>>>>> On Monday, November 17, 2025 at 9:55:49 AM UTC-7 [email protected] >>>>>>> wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> As per: https://github.com/jenkins-infra/helpdesk/issues/4870 >>>>>>>> >>>>>>>> * Issues have been enabled on jenkinsci/jenkins >>>>>>>> * Pinned issue created - >>>>>>>> https://github.com/jenkinsci/jenkins/issues/11301 >>>>>>>> * Jira banner enabled - >>>>>>>> https://issues.jenkins.io/secure/Dashboard.jspa >>>>>>>> >>>>>>>> Thanks >>>>>>>> Tim >>>>>>>> >>>>>>>> On Sunday, 16 November 2025 at 13:28:46 UTC [email protected] >>>>>>>> wrote: >>>>>>>> >>>>>>>>> > What is the plan with cross project issues? >>>>>>>>> >>>>>>>>> Added more info in https://github.com/jenkinsci/jep/pull/420 >>>>>>>>> >>>>>>>>> On Sunday, 16 November 2025 at 08:49:39 UTC [email protected] >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> > Is the information about other components lost after the >>>>>>>>>> migration? E.g., JENKINS-76249 has core, credentials-plugin, >>>>>>>>>> ssh-credentials-plugin. >>>>>>>>>> >>>>>>>>>> That's in the latest import (since we've included cli issues and >>>>>>>>>> kept the context, other components will now be there too) >>>>>>>>>> https://github.com/timja-org/jenkins-gh-issues-poc-11-15/issues >>>>>>>>>> >>>>>>>>>> e.g. >>>>>>>>>> https://github.com/timja-org/jenkins-gh-issues-poc-11-15/issues/40 >>>>>>>>>> >>>>>>>>>> > What is the plan with cross project issues? Is it still >>>>>>>>>> possible to connect them somehow in the affected repositories? >>>>>>>>>> >>>>>>>>>> There's two types I can think of right now: >>>>>>>>>> 1. Epics with children that span repositories >>>>>>>>>> >>>>>>>>>> Parent and child issues can be in different repositories, so one >>>>>>>>>> tracking issue can be filed in e.g. core for say Java EE 10 upgrade >>>>>>>>>> and >>>>>>>>>> then issues can be filed in the appropriate components and linked to >>>>>>>>>> the >>>>>>>>>> parent. >>>>>>>>>> >>>>>>>>>> 2. Issues that are filed potentially relating to multiple >>>>>>>>>> components. >>>>>>>>>> >>>>>>>>>> These really don't work that well in Jenkins Jira as notification >>>>>>>>>> is driven off of assignee, they get lost very easily and are most >>>>>>>>>> often >>>>>>>>>> misfiled. >>>>>>>>>> I went through most of the issues which had remoting and core >>>>>>>>>> components and the majority of them were not related to core. >>>>>>>>>> >>>>>>>>>> If it's an issue in a plugin then it should be filed there first. >>>>>>>>>> If it's determined that its an issue in core then either: >>>>>>>>>> * a targeted issue can be filed and a reference to the original >>>>>>>>>> issue in a comment or the description - I think the majority >>>>>>>>>> * it can be moved - this should only be done if it was misfiled, >>>>>>>>>> e.g. if people are going to keep hitting the bug and think its the >>>>>>>>>> plugin >>>>>>>>>> it should probably stay so people can find their way. >>>>>>>>>> >>>>>>>>>> On Sat, 15 Nov 2025 at 22:09, Ullrich Hafner < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> > How are you going to handle issues with both 'core' and >>>>>>>>>>> 'remoting' components (and similar overlaps)? >>>>>>>>>>> >>>>>>>>>>> They will all go to the jenkins repository if they have the core >>>>>>>>>>> component. (handled by the fact we are archiving the issues as part >>>>>>>>>>> of the >>>>>>>>>>> migration which prevents them showing up in searches). >>>>>>>>>>> >>>>>>>>>>> I'll do a bit of sweeping through the ones with multiple >>>>>>>>>>> components that are open and see if any can be assigned better. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Is the information about other components lost after the >>>>>>>>>>> migration? E.g., JENKINS-76249 has core, credentials-plugin, >>>>>>>>>>> ssh-credentials-plugin. >>>>>>>>>>> I don’t see this information in >>>>>>>>>>> https://github.com/timja-org/jenkins-gh-issues-poc-11-12/issues/5375 >>>>>>>>>>> >>>>>>>>>>> What is the plan with cross project issues? Is it still possible >>>>>>>>>>> to connect them somehow in the affected repositories? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> 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/AE9EC24D-1814-4F66-B566-A6B1F927A81B%40gmail.com >>>>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/AE9EC24D-1814-4F66-B566-A6B1F927A81B%40gmail.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/9e4b9323-3e24-42aa-8bbc-fb53b5d45b45n%40googlegroups.com >>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/9e4b9323-3e24-42aa-8bbc-fb53b5d45b45n%40googlegroups.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/348b583b-a68b-4512-8189-288569c0b20cn%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/348b583b-a68b-4512-8189-288569c0b20cn%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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BievQ3gQ6u6xgVCb6O%2BkR5PqtfRPYrpnKporyGcUW9AfZQ%40mail.gmail.com.
