Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

unable to open/view attachments through CSV imports in jira tickets

Hi Team,

 We are copying the data from one jira instance to our instance. We are unable to add the attachments to the tickets through CSV imports. As per Atlassian suggested , I have tried with the below file in the "Attachment" column in exported file, but the files are still showing errors.


12/06/2022 09:30 PM;;image-2022-11-28-11-04-44-590.png;https://username:password@


1 answer

0 votes
Darryl Lee Community Leader Dec 06, 2022

Hi @Lakshmi S - I think the problem is the way that you're specifying the username/password in the URL is not valid:


In fact, I don't think there's a way to link to a password-protected resource from a CSV file.

The way I've seen this done before is having to upload all attachments to a temporary web server that doesn't require any authentication. One solution might be something like an S3 bucket configured to be a static website.

You would have to do additional work to make to match up the S3 web URL for attachments with the correct issue in your CSV.

Then, when it comes time to do the import, you would only make it "public" for the duration of your import, and then turn it off.


If you can copy the files to your target server, there's another option (although with scant details):

You can also use the FILE protocol to access files in the import/attachments subdirectory of your Jira home directory.

Found here:

OH, I guess it would look like this:


So, that'd be handy. You'd probably want to keep things in folders named after issues though.

Suggest an answer

Log in or Sign up to answer