Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Jira return null values for issues


Well, my question is more theoretical as I do not have code to show and possibly look for the mistakes. 
To explain a bit. We have set up ETL to get all the data we have on JIRA(about 60k rows).
The problem is that when we run the ETL day by day there are lots of differences, last time it was in 10k records - this is very relevant to the dates based on the statuses in the history(in development date, under consideration date, ready to ship date, etc.)
Sometimes for some issues we get the correct dates, the next day they are "null", the day after they are again correct, but we are never able to capture the whole picture. 

Is it possibly because we make around 60k calls to the API for every single issue in the history?
Or maybe the problem is somewhere else.

One more question, can we make an export for 60k rows at once? If yes, how and if no, what is the alternative?

Thanks for you input!




Log in or Sign up to comment