Re: Migration from Jira to Github issues
Hi, It sounds good to me ! Thanks, Regards JB > Le 1 févr. 2021 à 09:38, Grzegorz Grzybek a écrit : > > Hello > > Some time ago[1] we were discussing the idea whether to move to Github issues > and move away from Jira. The main reason was related to registration/spam > problems at cloud Jira/Confluence. > I think all involved agreed that it's a good idea. > > I've prepared a raw tool[2] with only a `main()` method that uses 3 > configuration files: > * etc/users.properties which map Cloud Jira user UUIDs into names (please let > me know if it's desired or not) > * etc/application-template.properties, which should be copied to (now > .gitignored) etc/application.properties that configure github token, org and > repository > * data/*.xml which contains all Jira issues exported from "all issues report" > at Cloud Jira > > I don't want to migrate all the projects without some feedback ;) > For now I took PAXTRANSX Jira issues and I've imported them into my > project[3]. Please see if the format I used is sufficient. > > I used the unofficial Github API described here[4] which was also used when > Spring projects were migrating[5]. > Links to users and attachments still lead to Cloud Jira (just as with Spring > issues). > > I used jsoup to parse HTML comments and descriptions and I did trivial HTML → > Markdown translation, so at least all the formatting used in PAXTRANSX > project is preserved. When I see more formatting in other OPS4J projects, > I'll handle it. > > I want to start with projects like PAXJDBC, PAXJMS and PAXURL and at some > point migrate PAXWEB project (around the time I finally release Pax Web 8). > > looking forward to your feedback! > Grzegorz Grzybek > --- > [1]: https://groups.google.com/g/ops4j/c/RE_r3cxtwSQ > <https://groups.google.com/g/ops4j/c/RE_r3cxtwSQ> > [2]: https://github.com/ops4j/org.ops4j.tools/tree/master/jira2github > <https://github.com/ops4j/org.ops4j.tools/tree/master/jira2github> > [3]: https://github.com/grgrzybek/test2github/issues > <https://github.com/grgrzybek/test2github/issues> > [4]: https://gist.github.com/jonmagic/5282384165e0f86ef105 > <https://gist.github.com/jonmagic/5282384165e0f86ef105> > [5]: > https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues > > <https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues> > > -- > -- > -- > OPS4J - http://www.ops4j.org <http://www.ops4j.org/> - ops4j@googlegroups.com > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ops4j+unsubscr...@googlegroups.com > <mailto:ops4j+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ops4j/CAAdXmhqCh4UpLpyCVuXZ%2BrHe92DOnRiM511c6d3LkBz7R%3DJvyQ%40mail.gmail.com > > <https://groups.google.com/d/msgid/ops4j/CAAdXmhqCh4UpLpyCVuXZ%2BrHe92DOnRiM511c6d3LkBz7R%3DJvyQ%40mail.gmail.com?utm_medium=email_source=footer>. -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/04288C9A-14AB-4B64-A49F-07F51D3F06D6%40gmail.com.
Re: Migration from Jira to Github issues
Sounds like a good idea. To be honest, I would even okay with NOT migrating to much of the issues. There are a lot of "dead" ones and as long as we can preserve the JIRA ones as a reference a link might suffice as well. Am 01.02.21 um 09:38 schrieb Grzegorz Grzybek: Hello Some time ago[1] we were discussing the idea whether to move to Github issues and move away from Jira. The main reason was related to registration/spam problems at cloud Jira/Confluence. I think all involved agreed that it's a good idea. I've prepared a raw tool[2] with only a `main()` method that uses 3 configuration files: * etc/users.properties which map Cloud Jira user UUIDs into names (please let me know if it's desired or not) * etc/application-template.properties, which should be copied to (now .gitignored) etc/application.properties that configure github token, org and repository * data/*.xml which contains all Jira issues exported from "all issues report" at Cloud Jira I don't want to migrate all the projects without some feedback ;) For now I took PAXTRANSX Jira issues and I've imported them into my project[3]. Please see if the format I used is sufficient. I used the unofficial Github API described here[4] which was also used when Spring projects were migrating[5]. Links to users and attachments still lead to Cloud Jira (just as with Spring issues). I used jsoup to parse HTML comments and descriptions and I did trivial HTML → Markdown translation, so at least all the formatting used in PAXTRANSX project is preserved. When I see more formatting in other OPS4J projects, I'll handle it. I want to start with projects like PAXJDBC, PAXJMS and PAXURL and at some point migrate PAXWEB project (around the time I finally release Pax Web 8). looking forward to your feedback! Grzegorz Grzybek --- [1]: https://groups.google.com/g/ops4j/c/RE_r3cxtwSQ <https://groups.google.com/g/ops4j/c/RE_r3cxtwSQ> [2]: https://github.com/ops4j/org.ops4j.tools/tree/master/jira2github <https://github.com/ops4j/org.ops4j.tools/tree/master/jira2github> [3]: https://github.com/grgrzybek/test2github/issues <https://github.com/grgrzybek/test2github/issues> [4]: https://gist.github.com/jonmagic/5282384165e0f86ef105 <https://gist.github.com/jonmagic/5282384165e0f86ef105> [5]: https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues <https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues> -- -- -- OPS4J - http://www.ops4j.org <http://www.ops4j.org> - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com <mailto:ops4j+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/CAAdXmhqCh4UpLpyCVuXZ%2BrHe92DOnRiM511c6d3LkBz7R%3DJvyQ%40mail.gmail.com <https://groups.google.com/d/msgid/ops4j/CAAdXmhqCh4UpLpyCVuXZ%2BrHe92DOnRiM511c6d3LkBz7R%3DJvyQ%40mail.gmail.com?utm_medium=email_source=footer>. -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/e0fb37d4-ddf8-96a0-e981-1d04e295c83d%40googlemail.com.
Migration from Jira to Github issues
Hello Some time ago[1] we were discussing the idea whether to move to Github issues and move away from Jira. The main reason was related to registration/spam problems at cloud Jira/Confluence. I think all involved agreed that it's a good idea. I've prepared a raw tool[2] with only a `main()` method that uses 3 configuration files: * etc/users.properties which map Cloud Jira user UUIDs into names (please let me know if it's desired or not) * etc/application-template.properties, which should be copied to (now .gitignored) etc/application.properties that configure github token, org and repository * data/*.xml which contains all Jira issues exported from "all issues report" at Cloud Jira I don't want to migrate all the projects without some feedback ;) For now I took PAXTRANSX Jira issues and I've imported them into my project[3]. Please see if the format I used is sufficient. I used the unofficial Github API described here[4] which was also used when Spring projects were migrating[5]. Links to users and attachments still lead to Cloud Jira (just as with Spring issues). I used jsoup to parse HTML comments and descriptions and I did trivial HTML → Markdown translation, so at least all the formatting used in PAXTRANSX project is preserved. When I see more formatting in other OPS4J projects, I'll handle it. I want to start with projects like PAXJDBC, PAXJMS and PAXURL and at some point migrate PAXWEB project (around the time I finally release Pax Web 8). looking forward to your feedback! Grzegorz Grzybek --- [1]: https://groups.google.com/g/ops4j/c/RE_r3cxtwSQ [2]: https://github.com/ops4j/org.ops4j.tools/tree/master/jira2github [3]: https://github.com/grgrzybek/test2github/issues [4]: https://gist.github.com/jonmagic/5282384165e0f86ef105 [5]: https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/CAAdXmhqCh4UpLpyCVuXZ%2BrHe92DOnRiM511c6d3LkBz7R%3DJvyQ%40mail.gmail.com.
