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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,552,581
Community Members
 
Community Events
184
Community Groups

CSV Import Error: Cannot parse as attachment info Illegal character in path at index

Edited

Getting the following error trying to import an attachment url where the attachment url is composed of a link with a security access token query string:

2018-06-28 19:12:56,540 WARN - Cannot parse '08/02/2017 01:37:26 AM;jira.admin;v1-2 errorreport.html;https://accountname.blob.core.windows.net/container/folder/v1-2 errorreport.html?sv=2017-11-09&sr=c&sig=mn4shIaKOsipsXZt5ZhlTRnB5V9K1v4A7Ctg4cM%3D&se=2018-06-29T02%3A00%3A03Z&sp=r' as attachment info: Illegal character in path at index 81

 

What are the illegal characters in attachment urls?

1 comment

AhmadDanial
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 28, 2018

Hi, Stuart.

The Unable to import file attachment from CSV KB suggests that the special or reserved characters is the potential culprit to the error that we are seeing here. I would suspect that the following characters contributes the issue:

  • -
  • =
  • ?
  • &

Can we try to either rename the file or use the percent encoding before re-importing the attachment URL again?

Comment

Log in or Sign up to comment