Jira Connector Error - Illegal Character

LaurenSteds

Hello,

We are working on a bi-directional sync via Jira Connector and continue to receive this error when we try to push new tickets into Jira from our Smartsheet (which is successfully receiving Jira updates and updating existing tickets) -

JIRA rest client exception occurred while syncing issue. java.net.URISyntaxException: Illegal character in path at index 61: https://jira.publicismedia.com/secure/attachment/2976268/icon new normal.png

I can tell the space between 'icon' and 'new normal' is what is driving this error but I cannot understand where this URL or PNG are originating. I have tried creating new lines in my sheet, updating all free-form fields to not include spaces. I have no attachments to my ticket so I'm not sure if this URL is generating from the API call?

Would appreciate any help the community can provide as this is ALMOST across the finish line!

Georgie

Hi @LaurenSteds,

This error usually relates to images/icons used in your JIRA instance rather than attachments in Smartsheet. I recommend reaching out to your JIRA admin and asking them to remove all spaces from image/icon URLs attached to projects in JIRA.

Hope that helps!

Georgie

LaurenSteds

Thank you @Georgie. We figured out that it was the iconography used for the priority field driving this error so solved for that one but now onto the many field mapping issues thanks to our very customized Jira instance.

Thank you for taking the time to reply!

Georgie

Hi @LaurenSteds,

This error usually relates to images/icons used in your JIRA instance rather than attachments in Smartsheet. I recommend reaching out to your JIRA admin and asking them to remove all spaces from image/icon URLs attached to projects in JIRA.

Hope that helps!

Georgie

LaurenSteds

Thank you @Georgie. We figured out that it was the iconography used for the priority field driving this error so solved for that one but now onto the many field mapping issues thanks to our very customized Jira instance.

Thank you for taking the time to reply!

Georgie

Hi @LaurenSteds,

No problem, and thanks to you for confirming the resolution for the issue!

Georgie