You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently JIM doesn't support migrating attachments. One possible way to achieve this is to place the JIRA attachments in a special project folder/branch and then link to those.
The text was updated successfully, but these errors were encountered:
We were planning to leave the links as is and later update them after deciding the location of attachments. We would be dumping all attachments into some local machine for now. I am also planning to generate a mapping file which contains 3 columns - Issue ID, File Name, Attachment ID.
Using this mapping file and the attachments, we want to be able to later update the links in imported GH issues. Is there anything we can do now to make this process easier? (such as storing the comment id of attachment comment maybe?)
Perhaps we could create an index of them and/or download them all so that we can upload / fix links later? At least that way after a migration there's no dependencies on the old JIRA server?
Yes, we would be downloading them all. And, hence we will not have any dependency on the old JIRA server.
Later, at some point, we should be replacing the text in comments to correct the links. So, we need a way to get to the comment containing the attachment link. One way to go about this is to search for a string such as "Attached By" which might uniquely identify this comment. As you can see, this method is not fool-proof i.e., some other comment might also have such a string. So, how should we go about this?
Currently JIM doesn't support migrating attachments. One possible way to achieve this is to place the JIRA attachments in a special project folder/branch and then link to those.
The text was updated successfully, but these errors were encountered: