[JIRA Connector] Facing parsing issues with the Jira Connector

Forge Component
(16)
Published on 2018-12-04 by OutSystems R&D
16 votes
Published on 2018-12-04 by OutSystems R&D

Hi,

I am facing the below parsing issues when I am using the Jira connector issueSearch API. I fixed the first issue by changing the Work Ratio field to longint in issueFields structure and other one facing issue with the versions 

1) Failed to parse response of the method 'IssueSearch' of the 'OutSystemsJIRA' REST API:
Parsing 'issues[94].fields.workratio': JSON integer 9223372036854775807 is too large or small for an Int32. Path 'issues[94].fields.workratio', line 1, position 607737.
Parsing 'issues[94].fields.lastViewed': Unexpected token when deserializing object: Null. Path 'issues[94].fields.lastViewed', line 1, position 607755.
Parsing 'issues[94]': Unexpected token while deserializing object: EndObject. Path 'issues[94]', line 1, position 612649.

--- Fixed this by changing the datatype for Work Ratio from int to longint in issueFields


2)
Failed to parse response of the method 'IssueSearch' of the 'OutSystemsJIRA' REST API:
Parsing 'issues[84].fields.versions': Unexpected character encountered while parsing value: {. Path 'issues[84].fields.versions', line 1, position 483067.
Parsing 'issues[84].fields.versions[0]': After parsing a value an unexpected character was encountered: :. Path 'issues[84].fields.versions[0]', line 1, position 483073.


Any help on this.

Thank you in advance!


Hi, it seems like the versions list, within the fields object, is empty. so if you try to access it with its index, you'll face issues like this.