tJIRAInput issues

[Michele3]

Hello,

I am using Talend Open Studio for Big Data 7.3.1 for reading from Jira, using a JQL query. My problem is that there are some (small) differences between the number of tickets that the Talend component retrieves and the one I see when logging to the Jira webpage. Has anyone experienced the same issue?

Does the batch size affect the extraction result?

Thanks in advance,

Michele

[Anonymous]

Hello,

Could you please give us an example about your issue? Trouble screenshots will be preferred.

Best regards

Sabrina

[Michele3]

Hello Sabrina,

below you can find the component used in my job, which extracts 21610 rows, and the screenshot from the same search (JQL) on the web, which extracts 21879 tickets.

Could the tExtractJSONFields_1 component be the cause of the problem? Maybe because I set the length of a column smaller than the effective length of the values inside that column. Nevertheless, I see that the tJIRAInput component itself extracts 21610. In case of a problem in the tExtractJSONFields component I would expect to see less rows in output from that component.

Cheers,

Michele

[Michele3]

Screenshot from Jira.

[Michele3]

Parameters used for the Jira component in Talend.

[Anonymous]

Hello,

What does the missing 268 rows look like? Is there any an entity which is end with a backslash? Does it works with tREST component?

Best regards

Sabrina

[Michele3]

Hello Sabrina,

we haven't found any significant difference between the rows that are extracted and the ones that are not.

We have tried the tREST component and it works well, it extracts all the tickets (we have followed these instructions https://developer.atlassian.com/server/jira/platform/rest-apis/#uri-structure and examples https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/#searching-for-issues-ex...). We are using the same tExtractJSONFields as before, so it seems the problem is confined to the tJIRAInput component.

Best regards,

Michele