> This includes giving folks time (1-2 weeks at least) to review the final form of the migrated data and confirm that there are no substantial problems left, and that common use cases are supported
I've updated the schedule in https://github.com/jenkins-infra/helpdesk/issues/4870 To give people time to review the migration, the planned date is now Monday 24th November. The latest migration is: https://github.com/timja-org/jenkins-gh-issues-poc-11-14 New features: - Raw HTML is in the description and comments - metadata available for searching reported by and commented on - Improved description export handling code blocks better and noformat - Avatars for comments - Jira commenter now archives issues and pins the comment Example Jira comment: http://issues.jenkins.io/browse/TEST-298 (I think that's the right link, Jira isn't loading for me right now) > For example, https://github.com/jenkinsci/jep/blob/master/jep/238/README.adoc#how-do-i-find-issues-ive-reported-on-jira simply doesn't work Thanks, fixed now (https://github.com/jenkinsci/jep/pull/419) > Another problem is that none of the many copies of JENKINS-76266 in the latest import has correct formatting Looks fine in a migration from a couple of days ago: https://github.com/timja-org/jenkins-gh-issues-poc-11-12/issues/5279#issuecomment-3529586658 > I'd strongly prefer if content problems and common use cases would be addressed before scheduling the actual migration All known content problems had been resolved (except for raw xml / html directly in the Jira). > Would it be possible to at least attach a raw wikitext output inside a details block, so if something looks off, the correct version, even if unrendered, is quickly accessible This has been implemented, see https://github.com/timja-org/jenkins-gh-issues-poc-11-13/issues/634. It's in the "originally reported by" section. On Thu, 13 Nov 2025 at 18:16, 'Daniel Beck' via Jenkins Developers < [email protected]> wrote: > > > On Wed, Nov 12, 2025 at 1:57 PM Tim Jacomb <[email protected]> wrote: > >> Happy to push it back a week or some, from a migration script PoV we have >> everything we need. Herve is planning a couple of improvements to make the >> issue processing script faster. >> >> Last example migration: >> >> https://github.com/timja-org/jenkins-gh-issues-poc-11-06-a2/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen >> > > What motivates this aggressive schedule? > > I've yet to see a complete sample migration in which I haven't found > problems with basic formatting or use cases within minutes. For example, > https://github.com/jenkinsci/jep/blob/master/jep/238/README.adoc#how-do-i-find-issues-ive-reported-on-jira > simply doesn't work. It has numerous false positive findings (as it seems > to look for "reported", "by:" and username anywhere in the issue -- look > for your own username, and the top 3 issues aren't reported by you), and > wrapping it in quotes finds nothing. > > Another problem is that none of the many copies of JENKINS-76266 in the > latest import has correct formatting, which indicates code formatting > imports remain broken, making messages like > https://github.com/timja-org/jenkins-gh-issues-poc-11-06-a2/issues/375#issuecomment-3499805311 > useless. > https://github.com/jenkinsci/jep/blob/master/jep/238/README.adoc#the-description-doesnt-render-well-in-some-cases-what-gives > is just not a good answer IMO. Would it be possible to at least attach a > raw wikitext output inside a details block, so if something looks off, the > correct version, even if unrendered, is quickly accessible? > > I'd strongly prefer if content problems and common use cases would be > addressed before scheduling the actual migration. > > . > > > 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/CAMo7PtKwqM%3Dp__g4jov9tOGbBNwqwndx9SybLc9OL_-%2Bg64kVg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKwqM%3Dp__g4jov9tOGbBNwqwndx9SybLc9OL_-%2Bg64kVg%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/CAH-3BieCN407b-sFdQtfQUs2xFA8e5mXKvBS7NkxoKJAtR92Hg%40mail.gmail.com.
