nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JSON Parse Error with Atlassian Connector

Richard Thibault

I've installed Atlassian connector 3.2 and pointed it at my hosted Jira instance (firesolutions.atlassian.net). I can log in OK, but when I try to sync I get a JSON parse error:

org.codehaus.jettison.json.JSONException: Cannot find parser for field witch schema: FieldSchema{type=resolution, items=null, system=resolution, custom=null, customId=null}

I tried rolling back to version 3.0 but now I get a 303 during login:

Unexpected status code during login: 303

Kinda stuck here......any ideas on how to fix?

Accepted answers

jjaroczynski

Removing 'resolution' field from the 'edit issue' and 'create issue' screens solves the problem.

All comments

Junior Clarke

They changed the Eclipse Update site. Please use the following

http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6

I think its because of Jira 5.0 Compatibility changes.

Junior

Junior Clarke

They changed the Eclipse Update site. Please use the following

http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6

I think its because of Jira 5.0 Compatibility changes.

Junior

Junior Clarke

They changed the Eclipse Update site. Please use the following

http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6

I think its because of Jira 5.0 Compatibility changes.

Junior

jjaroczynski

Regarding 303 error, I saw few other reports like that. It looks like something changed on the hosted JIRA and old Connector version stopped working with OnDemand.

However all customers who switched to Connector 3.2.1 had not further issues.

I think you may be a victim of https://ecosystem.atlassian.net/browse/JRJC-134
Do you have 'resolution' field on the issue create screen?

Cheers,
Jacek

Richard Thibault

I do indeed have a Resolution field - not on the create screen, but the edit screen. Guess I'm out of luck until that bug is fixed?

jjaroczynski

I have reproduced the problem.

Do you really need 'resolution' field on the edit screen?

Can you also watch, vote and comment the https://ecosystem.atlassian.net/browse/JRJC-134?

jjaroczynski

Removing 'resolution' field from the 'edit issue' and 'create issue' screens solves the problem.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

connect

ide-connector