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 your account is linked as the original reporter/author with real mentions, like this example. https://github.com/mocobeta/migration-test-1/issues/111 If they do not disturb your inbox with spam notifications then the test is successful. With regard to attachments: > 1) create a (separate?) git repository or branch with a separate root in the lucene repository with all jira attachments upon importing them. > 2) there are about 7k issues with attachments in Jira. We can split them into 25-issue batches and ask the crowd to port them manually Thanks for your suggestion, I don't come up with other options either. Both would need others' permission and/or extra work, so I think we can't control the process and outcome. For 1), we'll need to ask infra to create a repository and run another long-running batch, and it'll complicate the migration instructions - we'll not be allowed to have access tokens to commit files to an ASF repo from a program. For 2), I'm not sure how many people want to volunteer for the manual work. I cannot promise it will be eventually done, then I would leave it as a limitation of the migration. If there are no controllable solutions (to me) on this, I may ask others if we should migrate existing issues to GitHub "even if we can't migrate any attachments and have to keep them in Jira forever". Let me keep myself neutral about the idea of migrating all Jira issues, sorry... I'm working on this not to push it but to provide information and gain a certain agreement. Tomoko 2022年6月25日(土) 16:12 Dawid Weiss <dawid.we...@gmail.com>: > > 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 then observe your >> inbox for a while, so that we can also test 2)? >> >> https://github.com/mocobeta/sandbox-lucene-10557/blob/main/migration/src/jira2github_import.py#L21 >> > > Emm.. sorry for being slow - what is it that you want me to do? :) > Unwatch->Ignore? > > >> In this Spring issue, the "attachment" link points to the original Jira >> file - so they still use Jira as a file server. >> > > Ahh... right. In that case I have two ideas: > > 1) create a (separate?) git repository or branch with a separate root in > the lucene repository with all jira attachments upon importing them. This > could be structured in subfolders, for example: > > jira/xyz/attachment-1.jpg > > if this repository is checked in to github, the links to attachment could > point at the "raw" git-serving service github offers. I'm not sure it emits > proper content-types (for images, etc). Alternatively, it could be > github-docs, which does serve them properly for static content. > > It will not support searches, of course, but it will be a consistent copy. > > 2) there are about 7k issues with attachments in Jira. We can split them > into 25-issue batches and ask the crowd to port them manually... It will > take time but once the issues are ported, it can be done incrementally over > a longer time stretch, no rush there. > > Dawid >
