error with Jira 5.0 Import Attachments via CSV HTTP protocol

Should it matter if I have subdirectories in the http:// import path?

For example, I have several thousand attachments to import that can be reached viahttp://<internal IP address>/SDE and beneath SDE have have several thousand folders with numbers. Those folders contain my attachments.

example directories:

/SDE/1234/word.doc

/SDE/4567/excelsheet.xlsx, etc.

If I use a csv string like :

'key-1, summary, http:// <internal IP address>/SDE/1234/word.doc'

'key-2, summary, http:// <internal IP address>/SDE/4567/excelsheet.xlsx'

Should this work? I am getting attachment errors when I try. I've had success with the File protocol on 5.1, but this system is 5.0 so I believe I need to use this HTTP protocol, correct?

2 answers

1 accepted

This widget could not be displayed.

Hi Johnson,

When performing the CSV import I would advise to upload your attachments to the <JIRA Home>/import/attachments/> folder or for http protocol upload to <JIRA_installation>/atlassian-jira/folder/ folder.

Then in your CSV file you can define the attachments like this: file://<attachmentname>.<extension>

For more details see

Regards,

Patina

This widget could not be displayed.

Hey,

It should work as long as your JIRA server (not where you use the browser or initiate the import) can access such http:// <internal IP address>/SDE/4567/excelsheet.xlsx without any issues. It's possible that your server cannot see <internal IP address> or it would need to authenticate. The authentication is not yet supported. These resources would have to be available anonymously. I recommend logging in to JIRA server via shell and running curl http:// <internal IP address>/SDE/4567/excelsheet.xlsx

If it works, then JIRA should be able to download and attach the attachments. If it still does not work, please raise a support request on support.atlassian.com and provide the logs from JIRA and from the importer.

Cheers,
Wojtek

Thank you Wojtek. I found another resolved issue where they said that the Issue Key required the Project prefix, and I added teh Issue Type to work properly.

Works now.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Aug 06, 2018 in Jira Service Desk

A is for Activate: Share your top Jira Service Desk onboarding tips for new users!

Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :).  In the spirit of this month's  august-challenge, we're sourcing stories of Jira Service Desk activation fro...

586 views 25 15
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you