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
