We use the Jira APIs to fetch json data on a daily basis.
We have never faced this issue before but we have 2 instances where the output JSON has a few extra parameters which donot come in on a daily basis.
This interferes with our flattening process.
Any idea why this may be happening ?
Solution for now :
We run the same job after 1-2 days and the data is fine again.
__________________________ more details ______________________
https://godaddy-services.atlassian.net/rest/api/3/search?expand=names,schema,changelog,transitions&fields=*all&startAt=300&maxResults=100&jql=project+%3D+IMAGE+and+updated+%3E+%222022-06-07+00%3A01%22+order+by+updated+ASC
We use something like the above.
Generally, on the daily load, from the above API, we donot get the roles part but intermittently, we got them last thurday because of which our flattening process failed. Below is a small section of the schema which was not fitting into our flattening process. We never had Managers, Production Fulfilment etc flowing into our process.
projectTypeKey:string,roles:struct<Administrators:string,Developers:string,Managers:string,Production Fulfilment:string,Service Desk Customers:string,Service Desk Team:string,Service Desk Team Multi Language:string,Service Desk Team Spanish:string,Supervisors:string,Tier 2 User:string,Training Fulfilment:string,atlassian-addons-project-access:string>,self:string,simplified:boolean,style:string,versions:array<string>>,reporter:struct<accountId:string,accountType:string,active:boolean,avatarUrls:struct<16x16:string,24x24:string,32x32:string,48x48:string>,displayName:string,self:string,timeZone:string>,resolution:struct<id:string,name:string,self:string>,
When we manually ran the above call, the same day, we had the issue pop up again.
When we run it the next day, we get the json in the older format like we wanted it to.
We would like to understand if there is something that we are doing wrong?
