Hello @MattWho , Thank you for the reply. Initially, I thought it would be best to include all the details in the ticket to avoid any confusion. Here's what I discovered: When the API was first executed, it fetched 100 records. Let's consider that all issues in JIRA contain different types of information, such as packages, bugs, epics, stories, and modules and they will have different columns . When fetching a small number of rows, the data appeared consistent, but when fetching data for 4-5 months, the data structure changed. For example, a bug might have 3 columns, a story might have 8, and epic might have 3. Consequently, all records had missing columns filled with null values. Here's an example: Bug 1: Columns A, B, C
Story 2: Columns A, B, C, D, E, F, G
Epic 3: Columns A, B As a result, the final records looked like this: {
A: Value,
B: Value,
C: Value,
D.:null,
E: null,
F: null,
G: null
},
{
A: Value,
B: Value,
C: Value,
D.:Value,
E: Value,
F: Value,
G: Value
},
{
A: Value,
B: Value,
C: null,
D.:null,
E: null,
F: null,
G: null
} To address this issue, I used the SplitJSON processor to split the records and process them individually . This resolved the issue. However, after implementing this solution, I encountered another issue where the choice list was not inserting records. I managed to handle this issue as well, and now everything is working fine.
... View more
