Degraded performance Customers may experience issues using Community search. Our team is investigating.
It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Hello all,
We are using JIRA-rest-java-client-api & core 2.0.0-m31.
Earlier, the custom fields were getting parsed correctly, but suddenly something changed in response data-type, and we started parsing the data improperly. Some parsing logic from JSON data is there in our code.
For e.g.
Actual JSON object received from Rest client:
{"self":"link_to_self","value":"Target","id":"1111"}
Value obtained by correct parsing based on custom field schema: Target
something changed and our parsing logic failed, and the value obtained as a result of parsing:
{"self":"link_to_self","value":"Target","id":"1111"}
We suspect either of the following change happenned on JIRA server side:
I tried searching relevant release note in https://developer.atlassian.com/jiradev/latest-updates/preparing-for-jira-7-0/jira-7-0-api-changes but didn't succeed.
Can anyone guide what changed in this case, and how to catch such issue pro-actively. Any link to the relevant documentation would be helpful.
"schema": { "type": "array", "items": "string", "custom": "com.atlassian.jira.plugin.system.customfieldtypes:multiselect", "customId": 1234 }
"schema": { "type": "array", "items": "option", "custom": "com.atlassian.jira.plugin.system.customfieldtypes:multiselect", "customId": 1234 }
What caused the change in the value of field "items" from "string" to "option"?
Er, your parsing results have not changed.
What it actually looks like is you've upgraded JIRA from 4.2 - before 4.2, select options were strings, after 4.2, they changed to options.
But Cloud is kept on the latest version at all times, and that's presented select lists as options over REST for many years.
So I think the question is actually what have you changed on your side?
I was referring to the whole of JIRA. If you have not changed the version of JIRA, then there are two other possibilities 1) You have a custom REST add-on which you have changed 2) Your external code that is calling REST has changed
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreAs a Jira power user, I was at first doubtful that Trello could benefit my workflow. Jira already uses boards (ones you can customize!), so why would I even need to use Trello?! In this post you will...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.