-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Best practice to import attachments with jiraone export file #144
Comments
Hey @kalupator To do that in # previous import statement
issue_export(jql=jql, extension="csv", final_file="export-test", allow_media=True) The argument |
Thanks for the answer! I will check it as soon as possible and write the result. |
@princenyeche, I tried to install allow_media=True. |
@kalupator I believe that's the username. If your site allows usernames, that should be how to auth it to allow attachments extracted from one site to another. |
@princenyeche |
Yeah, I found the problem here. The code uses an index when it should not. I've fixed it and will push the fix in the next update. |
@princenyeche |
Hello!
In the prepared by jiraone csv\json export file, links to attachments from the old jira look like this:
https://oldjira.domain.com/secure/attachment/11853/MyFile.docx
But when importing a file into a new Jira, the attachments file cannot be downloaded from the old Jira, because authentication is required in the old Jira.
I have already dealt with this before and solved this problem in the following way:
For each attachment link I added a login and password for old jira in the following way: ?os_username=USER&os_password=PWD.
For example:
https://oldjira.domain.com/secure/attachment/11853/MyFile.docx?os_username=USER&os_password=PWD
After that, when importing a file in the new Jira, attachments were downloaded from the old Jira.
I want to understand if there is any solution for jiraone when preparing the export file?
What is the best practice for importing attachments with jiraone prepared export file?
Thanks!
The text was updated successfully, but these errors were encountered: