Re: A prototype migration tool Jira to GitHub

Hello - it's my first and last call for volunteers for the GitHub migration. Sorry, I know few people may be interested in this work. But I didn't want just to complain as "no one helped me so I had to take over all pains on my own" without explicitly calling for help. These are tasks that should

Re: A prototype migration tool Jira to GitHub

It seems there are no major objections? A status update - we now have a public ASF repository for the migration and all work will be done under it, outside the main lucene repo/Jira/dev list. https://github.com/apache/lucene-jira-archive I'm not fully sure how many people are interested in this

Re: A prototype migration tool Jira to GitHub

I looked at the first random issue and noticed these (perhaps known) issues - https://github.com/mocobeta/sandbox-lucene-10557/issues/10838 1) lists are converted into bold blocks (without the list): https://github.com/mocobeta/sandbox-lucene-10557/issues/10838#issuecomment-1166777318 2) inline

Re: A prototype migration tool Jira to GitHub

I finished the second prototype. With a few exceptions, almost all existing issues were successfully migrated into the test repo. You can browse/search them. https://github.com/mocobeta/sandbox-lucene-10557/issues Some limitations in the first prototype have been addressed. For example, we can

Re: A prototype migration tool Jira to GitHub

> It looks like the GitHub Danger Zone can transfer a repository? "Transferring a repository" creates another repository different from apache/lucene. It'd make the migration process easy though, is it our intention to have an external repository for old issues? Tomoko 2022年6月27日(月) 8:24

Re: A prototype migration tool Jira to GitHub

It looks like the GitHub Danger Zone can transfer a repository? It's not clear if it can go from Personal -> Organization though. I see Personal -> Personal and Organization -> Organization. https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository

Re: A prototype migration tool Jira to GitHub

> > 2022年6月27日(月) 5:16 Michael Sokolov : > >> as for this access control/script monitoring problem, I wonder whether >> we could import all the issues into a new github repo owned by >> whomever is running the script, and then transfer from there to the >> lucene repo? It would be an extra step

Re: A prototype migration tool Jira to GitHub

2022年6月27日(月) 5:16 Michael Sokolov : > as for this access control/script monitoring problem, I wonder whether > we could import all the issues into a new github repo owned by > whomever is running the script, and then transfer from there to the > lucene repo? It would be an extra step involving

Re: A prototype migration tool Jira to GitHub

as for this access control/script monitoring problem, I wonder whether we could import all the issues into a new github repo owned by whomever is running the script, and then transfer from there to the lucene repo? It would be an extra step involving another script (or something), but maybe(?)

Re: A prototype migration tool Jira to GitHub

I may have to share another practical consideration on the migration that I haven't mentioned yet. We are not allowed to have admin access to the lucene GitHub repo, so can't run the import job(s) on ourselves. We'll have to make a tool with clear instructions for the migration and pass it to

Re: A prototype migration tool Jira to GitHub

Hi Dawid, > Emm.. sorry for being slow - what is it that you want me to do? :) Unwatch->Ignore? I'm sorry for being ambiguous. Could you set your notification setting on the repository as "Participating and @mentions"? In the testing of migration scripts, I will import many fake issues where

Re: A prototype migration tool Jira to GitHub

Hi Tomoko, > There are two ways to receive notifications as you know, 1) watch all > activities and 2) receive notifications only when you are mentioned > (default). > I excluded your github account from marking up with backticks `` to create > hyperlinks. Could you unwatch the repo again and

Re: A prototype migration tool Jira to GitHub

Hi Houston and Dawid, Thanks so much for your help. I might use other test repos but when I try to migrate a large portion of issues I post them to https://github.com/mocobeta/sandbox-lucene-10557. > So did I. There are two ways to receive notifications as you know, 1) watch all activities and

Re: A prototype migration tool Jira to GitHub

> I've subscribed to all notifications for that sandbox-lucene-10557 repo. Let > me know if you are going to create a different repo and I'll subscribe to > that as well. So did I. How did they import attachment with this API? I can't find this anywhere and they definitely did it somehow.

Re: A prototype migration tool Jira to GitHub

> > Is there anybody who kindly provides a github account to make sure that > "any notifications are never triggered" when executing migration? I > confirmed this with my account, just wanted to test it with other one or > two accounts. > I've subscribed to all notifications for that

Re: A prototype migration tool Jira to GitHub

I started to play around with the (unofficial) Issue Import API and so far so good. - Original timestamps (created, updated) are preserved - An issue and its comments can be imported with one post request; importing is done asynchronously but

Re: A prototype migration tool Jira to GitHub

FWIW I don't mind receiving these one-time notifications for the purpose of the migration. On Fri, Jun 24, 2022 at 12:58 PM Tomoko Uchida wrote: > > If you could give me some "example mail", I can add a "feed to trash" > sieve rule before you start it. > > If we decide to migrate all Jira

Re: A prototype migration tool Jira to GitHub

> If you could give me some "example mail", I can add a "feed to trash" sieve > rule before you start it. If we decide to migrate all Jira issues to GItHub with reporter/author account re-mapping (hyperlinks), and we still cannot find a workaround not to trigger notifications, I'll let you all

Re: A prototype migration tool Jira to GitHub

Hi, Am 23.06.2022 um 19:09 schrieb Tomoko Uchida: uschindler,Uwe Schindler,2474 If you could give me some "example mail", I can add a "feed to trash" sieve rule before you start it. We have 109158 resources (10608 issues + 98550 comments) in total. With the default rate limit of 5000 reqs

Re: A prototype migration tool Jira to GitHub

> * I don’t think a flood of notifications from the import is a problem. It’s a one time hassle, and having the actual user links is nice for GitHub’s cross linking system. > I agree with Ryan - I'd be willing to bulk-delete 1000 notifications if it means preserving hyperlinks to people I'd

Re: A prototype migration tool Jira to GitHub

It seems not new - I don't figure out why this is not published as a public API yet but according to the comments there, it could be buggy/unstable (still worth a try to me). 2022年6月24日(金) 0:26 Tomoko Uchida : > I just browsed through this article about the "import issues" API (looks > pretty

Re: A prototype migration tool Jira to GitHub

I just browsed through this article about the "import issues" API (looks pretty new and on technical preview status?) https://gist.github.com/jonmagic/5282384165e0f86ef105 Seems it solves many of our considerations - preserving original timestamp, bulk importing issue comments, and not triggering

Re: A prototype migration tool Jira to GitHub

oh phew! glad to hear this was expected On Thu, Jun 23, 2022 at 10:17 AM Tomoko Uchida wrote: > > > Many comments were lost in the transfer. The last one in the copy is > > only about 1/4 of the way through this gigantic issue. This really is > > a blocker I think. > > I limited the number of

Re: A prototype migration tool Jira to GitHub

> Many comments were lost in the transfer. The last one in the copy is > only about 1/4 of the way through this gigantic issue. This really is > a blocker I think. I limited the number of comments per issue up to ten for testing. We can migrate literally all comments - one by one. Tomoko

Re: A prototype migration tool Jira to GitHub

Hi, I have little now to carefully read/respond to all replies right now, but just wanted to answer this. > Will it be possible to preserve links from issues -> pull requests? Yes it's a bit cumbersome (and it could be difficult to make sure that all links to PRs are covered - it's not solid

Re: A prototype migration tool Jira to GitHub

Interesting, thanks Rob. I see the attachments have been ported in that article as well - something the official API is not able to do. https://jira.spring.io/browse/DATACMNS-617?redirect=false https://github.com/spring-projects/spring-data-commons/issues/1080 Dawid On Thu, Jun 23, 2022 at 3:26

Re: A prototype migration tool Jira to GitHub

I didn't read the entire thread, so apologies if this is a duplicate: Did you check https://spring.io/blog/2021/01/07/spring-data-s-migration-from-jira-to-github-issues They especially write there is an api that doesn't trigger notifications. It is documented here:

Re: A prototype migration tool Jira to GitHub

Yes thank you! You say this is not difficult, but it looks like a big job to me! Here are a bunch of things I noticed that we would ideally address (from looking at one long and complex issue, LUCENE-9004). I wouldn't be so bold as to say these should block us from proceeding if they're not

Re: A prototype migration tool Jira to GitHub

This is great work Tomoko! A couple minor thoughts: * I don’t think a flood of notifications from the import is a problem. It’s a one time hassle, and having the actual user links is nice for GitHub’s cross linking system. * Do you have an estimate for how many api calls are needed? How many

A prototype migration tool Jira to GitHub

Hi all, again - this is about GitHub migration. We have a large disagreement on whether we should migrate existing Jira issues (including all closed issues) to GitHub or not. I drafted a tiny migration tool [1] to see how it looks if we move Jira issues to GitHub, and tried to migrate a small